H3C SeerEngine-SDWAN
Deployment Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W100-20250407

 

Contents

Introduction· 1

Preparing for installation· 2

Server requirements· 2

Hardware requirements· 2

Software requirements· 2

Installation procedure· 3

Client requirements· 3

Pre-installation checklist 3

Verifying the software packages· 4

Planning disk partitions· 4

Deploying SeerEngine-SDWAN·· 7

Installation and deployment procedure· 7

Deploying SeerEngine-SDWAN· 7

Deploying the UDTP_Base component 7

Accessing the convergence deployment page· 8

Managing the installation packages· 8

Selecting applications· 9

Selecting installation packages· 9

Configuring resources· 10

Configuring parameters· 11

View component details· 12

Accessing the SeerEngine-SDWAN page· 13

Registering the software· 14

Installing the license on the license server 14

Obtaining the license authorization· 14

Backing up and restoring SeerEngine-SDWAN configuration· 15

Upgrading SeerEngine-SDWAN·· 16

Uninstalling SeerEngine-SDWAN·· 17

Introduction

This document describes the procedure for installing SeerEngine-SDWAN, which acts as the WAN controller for service automation and intelligent traffic engineering in a branch network scenario.

SeerEngine-SDWAN is deployed on Matrix, which is a Kubernetes-based platform that orchestrates and schedules Docker containers. On Matrix, you can build Kubernetes clusters, deploy microservices, and implement O&M monitoring of systems, Docker containers, and microservices.

 

Preparing for installation

Server requirements

Hardware requirements

You must deploy, upgrade, and uninstall the SeerEngine-SDWAN component from Matrix. Before deploying the SeerEngine-SDWAN component, make sure the Unified Platform UDTP_Base component has been successfully deployed. The component supports both standalone deployment and cluster deployment on physical servers and virtual machines (VMs). In standalone deployment mode, prepare one server. In cluster deployment mode, prepare a minimum of three servers. You can obtain hardware configuration requirements through either of the following methods:

·     Access http://iservice.h3c.com, open the hardware resource calculation page, and then enter the required information for calculation. The calculation result is for reference only.

·     Contact Technical Support.

 

CAUTION: ·     Deployment on physical hosts is recommended for a middle-/large-scale scenario (with more than 200 devices). ·     The CPU, memory, and disk resources allocated to a VM must meet the recommended capacity requirements. Make sure physical resources of the corresponding capacities exist. Do not enable the overcommitment mode, which allocates resources more than resources available. Additionally, you must reserve resources for VMs. If you do not do that, the system environment will be unstable. ·     The etcd partition can share a physical drive with other partitions. As a best practice, use a separate drive for the etcd partition. ·     To deploy the SeerEngine-SDWAN controller on a VM managed by VMware, you must enable the promiscuous mode and forged transmits on the host where the VM resides.

 

Software requirements

To deploy SeerEngine-SDWAN, you must first deploy Matrix, because SeerEngine-SDWAN must be deployed from Matrix. When installing SeerEngine-SDWAN, you must select the application packages to install as shown in Table 1. First, bulk upload the installation packages on the convergence deployment page of Matrix.

 

NOTE: ·     A Unified Platform application package name might vary by software version. For more information, see the product release notes. This section uses SeerEngine-SDWAN R71xx together with Unified Platform E71xx as examples. ·     Table 1 shows the application package names, where version represents the software version number and platform represents the CPU architecture. ·     For the system to run correctly, you must install the required application packages. You can install optional application packages as needed to use related features.

 

Table 1 Application installation packages

Installation package name	Description	Remarks
UDTP_Base_version_platform.zip	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.
BMP_Common_version_platform.zip	Provides dashboard management, alarms, alarm aggregation, and alarm subscription.	Required.
BMP_Connect_version_platform.zip	Provides hierarchical site management, WebSocket channel management, and NETCONF channel management.	Required.
WAN_WVAS_version_platform.zip	Provides value-added WAN services for the system.	Required.
BMP_ExtensionRDR_version_platform.zip	Provides remote disaster recovery (RDR), snapshot rollback, certificate services, self-monitoring, intelligent algorithm library, single sign-on, and password platform.	Optional.
H3C_SEERENGINE_SDWAN-version_platform.zip	Provide branch WAN network management services for the system.	Required.

 

Installation procedure

For steps of deploying a new SD-WAN environment, see Table 2.

Table 2 Environment deployment procedure

Step	Remarks
1.     Install the NingOS operating system	For more information, see H3C Unified Platform Deployment Guide.
2.     Deploy Matrix	For more information, see H3C Unified Platform Deployment Guide.
3.     Deploy the SeerEngine-SDWAN component	For more information, see "Deploying SeerEngine-SDWAN."

 

Client requirements

You can access SeerEngine-SDWAN directly through a browser and do not need to install a client. As a best practice, use Google Chrome 96, Firefox 97, or a higher version.

Pre-installation checklist

Table 3 Pre-installation checklist

Item		Requirements
Server	Hardware	The CPU, memory, disk, and NIC requirements for installing SeerEngine-SDWAN are met.
	Software	The system time settings are configured correctly. As a best practice, configure NTP on each node and specify the same time source for all the nodes.
Client		The browser version meets the requirements.

 

To ensure the 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 supports of the server/RAID controller vendors.

Verifying the software packages

Before installing 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

BMP_Report_E0722_x86.zip     UDTP_Core_E0722_x86

…Omitted…

2.     View the MD5 values of the installation packages, for example, UDTP_Core_E0722_x86.zip.

[root@node1~]# md5sum UDTP_Core_E0722_x86.zip

2b8daa20bfec12b199192e2f6e6fdeac  UDTP_Core_E0722_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.

Planning disk partitions

Plan the RAID arrays and partitions for disks based on different service scales and server configuration requirements.

Table 4 Disk RAID and partition planning (200 resources)

Disk RAID planning	Mount point	Minimum capacity	Boot modes	File system	Remarks
2 × 1 TB, RAID1	/var/lib/docker	70 GiB	BIOS mode, UEFI mode	ext4	N/A
	/boot	1024 MiB	BIOS mode, UEFI mode	ext4	N/A
	swap	1024 MiB	BIOS mode, UEFI mode	swap	N/A
	/var/lib/ssdata	237 GiB	BIOS mode, UEFI mode	ext4	If the disk space is sufficient, you can expand the capacity appropriately.
	/var/lib/ssdata/logcenter	400 GiB	BIOS mode, UEFI mode	ext4	Use this partition to store log data. If the disk space is sufficient, you can expand the capacity appropriately.
	N/A	80 GiB	BIOS mode, UEFI mode	ext4	If the disk space is sufficient, you can expand the capacity appropriately.
	/opt/matrix/app/data/base-service/backupRecovery	30 GiB	BIOS mode, UEFI mode	ext4	Use this partition to store backup service data. If this partition is not created, the backup service data is stored in the root partition. If this partition is created, the backup service data is stored in this partition. When you create this partition, its disk space is allocated from the root partition. For example, when setting this partition size to 100 GiB, adjust the root partition size from 700 GiB to 600 GiB.
	/var/lib/ssdata/middleware/seaio	130 GiB	BIOS mode, UEFI mode	ext4	N/A
	/boot/efi	200 MiB	UEFI mode	EFI	N/A
2 × 50 GB, RAID1	/var/lib/etcd	50 GiB	BIOS mode, UEFI mode	ext4	As a best practice, mount a separate disk (a minimum of 51 GB is required).

 

Table 5 Disk RAID and partition planning (2000 resources)

Disk RAID planning	Mount point	Minimum capacity	Boot modes	File system	Remarks
2 × 1.2 TB, RAID1	/var/lib/docker	70 GiB	BIOS mode, UEFI mode	ext4	N/A
	/boot	1024 MiB	BIOS mode, UEFI mode	ext4	N/A
	swap	1024 MiB	BIOS mode, UEFI mode	swap	N/A
	/var/lib/ssdata	337 GiB	BIOS mode, UEFI mode	ext4	If the disk space is sufficient, you can expand the capacity appropriately.
	/var/lib/ssdata/logcenter	440 GiB	BIOS mode, UEFI mode	ext4	Use this partition to store log data. If the disk space is sufficient, you can expand the capacity appropriately.
	N/A	80 GiB	BIOS mode, UEFI mode	ext4	If the disk space is sufficient, you can expand the capacity appropriately.
	/opt/matrix/app/data/base-service/backupRecovery	90 GiB	BIOS mode, UEFI mode	ext4	Use this partition to store backup service data. If this partition is not created, the backup service data is stored in the root partition. If this partition is created, the backup service data is stored in this partition. When you create this partition, its disk space is allocated from the root partition. For example, when setting this partition size to 100 GiB, adjust the root partition size from 700 GiB to 600 GiB.
	/var/lib/ssdata/middleware/seaio	130 GiB	BIOS mode, UEFI mode	ext4	N/A
	/boot/efi	200 MiB	UEFI mode	EFI	N/A
2 × 50 GB, RAID1	/var/lib/etcd	50 GiB	BIOS mode, UEFI mode	ext4	As a best practice, mount a separate disk (a minimum of 51 GB is required).

 

CAUTION: ·     If you deploy other components in addition to SeerEngine-SDWAN, determine the size to be used by these components, and then expand the space as needed. ·     The /opt/matrix/app/data/base-service/backupRecovery partition is the capacity required for deploying Unified Platform and the SDWAN controller. If you deploy other components, determine the size to be used by these components, and then expand the space as needed.

 

 

Deploying SeerEngine-SDWAN

As a best practice, deploy SeerEngine-SDWAN as a component on the convergence deployment page of Matrix. After deployment, SeerEngine-SDWAN is deployed on the host as a container.

Installation and deployment procedure

Table 6 Installation and deployment steps

Step	Task	Remarks
1.     Deploying the UDTP_Base component	Log in to Matrix and deploy the UDTP_Base_<version>.zip component.	Required.
2.     Accessing the convergence deployment page	Click Convergence Deployment.	Required.
3.     Managing the installation packages	Select packages required for deployed components.	Required. For the required installation packages, see Table 7.
4.     Selecting applications	Select the WAN branch application group.	Required.
5.     Selecting installation packages	Select the installation package versions for the dependencies and controller.	Required.
6.     Configuring resources	Select a resource level based on the scale supported by the hardware.	Required.
7.     Configuring parameters	Configure the nodes for controller deployment and the MSP mode.	Required.

 

Table 7 Component installation package

Installation option	Component name	Component installation package name
SD-WAN	SeerEngine-SDWAN	H3C_SEERENGINE_SDWAN-version.zip

 

Deploying SeerEngine-SDWAN

Deploying the UDTP_Base component

Access the application deployment page and deploy the UDTP_Base component:

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

The ip_address parameter specifies the northbound service VIP.

2.     Access the Deploy > Applications page.

Figure 1 Applications page

 

3.     Click Deploy Applications to access the software package management page. Then, click Upload to upload the UDTP_Base_<version>.zip installation package.

4.     Click Next to access the parameter configuration page, where you can edit the parameters as needed.

Figure 2 Configuring parameters

 

5.     Click Deploy to start installing the UDTP_Base_<version>.zip component.

Once the installation is complete, the Convergence Deployment menu item will appear.

Accessing the convergence deployment page

Access the Deploy > Convergence Deployment page.

Figure 3 Convergence deployment page

 

Managing the installation packages

Click Packages Management to access the installation package management page.

On this page, you can upload and delete installation packages. The installation package list displays names, versions, sizes, creation time, and other information of the uploaded installation packages. You can bulk upload application installation packages. After the installation packages are uploaded, click  to return to the deployment management page.

Figure 4 Uploading installation packages

 

Selecting applications

Click Install to access the Select Applications page, where you can perform the following tasks:

·     Select application scenarios as needed. After you select application scenarios, the page will display applications related to Unified Platform and the selected components.

By default, the applications for all scenarios are displayed, including applications related to Unified Platform and other components.

Figure 5 Selecting applications

 

·     In the Unified Platform area, select the applications you want to deploy (dependent applications will be selected by default), and click Next to access the Select Packages page.

Selecting installation packages

On the Select Packages page, select the application package version numbers, and click Next to access the Configure Resources page.

Figure 6 Selecting installation packages

 

Configuring resources

1.     On the Configure Resources page, select a resource level based on the scale supported by the hardware.

¡     When the device scale is less than 200, as a best practice, select the small scale for the Unified Platform + basic network management service set, and select the small scale for the WAN branch service set.

¡     When the device scale exceeds 200, as a best practice, select the default scale for the Unified Platform + basic network management service set, and select the default scale for the WAN branch service set.

2.     After selecting the resource levels, click Next to access the Configure Parameters page.

Figure 7 Configuring resources

 

Configuring parameters

	TIP: You can select the nodes to be bound only when worker nodes exist. When binding a node, make sure the selected node is in normal state. You can select only one or three nodes. You cannot select both master nodes and worker nodes.

 

1.     On the Configure Parameters page, configure relevant parameters for each node as needed.

2.     To deploy the SDWAN MSP scenario, turn on the MSP Scenario switch.

Figure 8 Configuring parameters

 

3.     Click Deploy. On the Confirm Parameters page that opens, you can confirm deployed and undeployed nodes of dependencies.

Figure 9 Confirming parameters

 

Figure 10 Deploying components

 

View component details

1.     After deployment is completed, click  to the left of a component on the component management page to expand the component information, as shown in Figure 11.

2.     Click the Details icon in the Actions column to view node binding information and MSP scenario deployment information.

Figure 11 Managing components

 

Figure 12 Component details

 

Accessing the SeerEngine-SDWAN page

After deployment is completed, access the deployment management page of Unified Platform, and click the Home tab to access the SeerEngine-SDWAN page as shown in Figure 13.

Figure 13 Accessing the SeerEngine-SDWAN page

 

Registering the software

The SeerEngine-SDWAN product requires a license to operate normally after it is installed and deployed.

Installing the license on the license server

For more information about requesting and installing the license, see H3C Software Product Remote Licensing Guide.

Obtaining the license authorization

After installing the license for the product on the license server, you only need to connect to the license server from the license management page to obtain the license authorization. To do that, perform the following tasks:

1.     Log in to the system.

2.     On the top navigation bar, click System.

3.     From the navigation pane, select License > License Information.

Figure 14 License information page

 

4.     Configure the license server parameters on the page.

Table 8 describes each parameter.

Table 8 Parameters

Parameter	Description
IP Address	Specify the IP address configured on the license server used for internal communication in the cluster where Unified Platform and SeerEngine-SDWAN are deployed.
Port	Specify the service port number of the license server. The default value is 5555.
Username	Specify the username configured on the license server.
Password	Specify the user password configured on the license server.

 

5.     SeerEngine-SDWAN automatically obtains licensing information after connecting to the license server.

 

Backing up and restoring SeerEngine-SDWAN configuration

You can back up and restore the SeerEngine-WAN component on Unified Platform. For more information, see H3C Unified Platform Deployment Guide.

Upgrading SeerEngine-SDWAN

On Matrix, you can upgrade the SeerEngine-SDWAN component with its configuration retained. Do not back up or restore data during the upgrade process.

To upgrade SeerEngine-SDWAN:

1.     In the address bar of the browser, enter https://ip_address:8443/matrix/ui to log in to Matrix, where the ip_address parameter specifies the configured northbound service VIP.

2.     Access the Deploy > Convergence Deployment page.

3.     Click the  icon to the left of the SDWAN branch component to expand the component information.

Figure 15 Deployment management page (1)

 

4.     Click the Upgrade icon  in the Actions column for an application to access the upgrade page.

Figure 16 Deployment management page (2)

 

5.     Click Upload. Upload the target installation packages. Select the installation packages to be upgraded, and then click Upgrade to upgrade the corresponding applications.

Figure 17 Upgrading components (1)

 

6.     On the upgrade page, you can view the specific upgrade progress. The success prompt will appear after the upgrade is complete.

7.     After the upgrade, clear the browser cache before you log in to the system again as a best practice.

 

Uninstalling SeerEngine-SDWAN

1.     Log in to Matrix. On the top navigation bar, click DEPLOY. From the navigation pane, select Convergence Deployment.

2.     Select the components you want to uninstall, and then click Uninstall to uninstall the specified components.

Figure 18 Uninstalling components