Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-Text | 1.18 MB |
Contents
Installing the activation file on the license server
Backing up and restoring SeerEngine-SDWAN components
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 core network or branch network scenario.
Preparing for installation
Hardware requirements
SeerEngine-SDWAN can be deployed on a single server or on a cluster of three or more servers and can be deployed on a physical server or on a VM. Table 1 describes the hardware requirements for installing SeerEngine-SDWAN on a physical server.
Table 1 Hardware requirements for standalone deployment (managing a maximum of 200 resources)
|
Item |
Requirements |
|
CPU |
x86-64 (Intel Xeon v3) 16 cores 2.0 GHz or above |
|
Memory |
120 GB or above |
|
Drive |
The drives must be configured in RAID 1, 5, or 10. The storage controller must have a 1GB cache, support power fail protection, and have a supercapacitor in place. · Drive configuration option 1: ¡ System drive: SSDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: SSDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) · Drive configuration option 2: ¡ System drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) |
|
NIC |
Non-redundancy mode: 1 × 1 Gbps or above Ethernet ports Redundancy mode: 2 × 1 Gbps Linux bonding interfaces (mode2 or mode4 is recommended) |
Table 2 Hardware requirements for standalone deployment (managing a maximum of 2000 resources)
|
Item |
Requirements |
|
CPU |
x86-64 (Intel Xeon v3) 20 cores 2.0 GHz or above |
|
Memory |
152 GB or above |
|
Drive |
The drives must be configured in RAID 1, 5, or 10. The storage controller must have a 1GB cache, support power fail protection, and have a supercapacitor in place. · Drive configuration option 1: ¡ System drive: SSDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: SSDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) · Drive configuration option 2: ¡ System drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) |
|
NIC |
Non-redundancy mode: 1 × 1 Gbps or above Ethernet ports Redundancy mode: 2 × 1 Gbps Linux bonding interfaces (mode2 or mode4 is recommended) |
Table 3 Hardware requirements for cluster deployment (managing a maximum of 200 resources)
|
Item |
Requirements |
|
CPU |
x86-64 (Intel Xeon v3) 14 cores 2.0 GHz or above |
|
Memory |
104 GB or above |
|
Drive |
The drives must be configured in RAID 1, 5, or 10. The storage controller must have a 1GB cache, support power fail protection, and have a supercapacitor in place. · Drive configuration option 1: ¡ System drive:SSDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: SSDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) · Drive configuration option 2: ¡ System drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) |
|
NIC |
Non-redundancy mode: 1 × 1 Gbps or above Ethernet ports Redundancy mode: 2 × 1 Gbps Linux bonding interfaces (mode2 or mode4 is recommended) |
Table 4 Hardware requirements for cluster deployment (managing a maximum of 2000 resources)
|
Item |
Requirements |
|
CPU |
x86-64 (Intel Xeon v3) 18 cores 2.0 GHz or above |
|
Memory |
136 GB or above |
|
Drive |
The drives must be configured in RAID 1, 5, or 10. The storage controller must have a 1GB cache, support power fail protection, and have a supercapacitor in place. · Drive configuration option 1: ¡ System drive:SSDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: SSDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) · Drive configuration option 2: ¡ System drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 2.4 TB. ¡ etcd drive: 7.2K RPM or above HDDs configured in RAID that provide a minimum total drive size of 50 GB. (Installation path: /var/lib/etcd.) |
|
NIC |
Non-redundancy mode: 1 × 1 Gbps or above Ethernet ports Redundancy mode: 2 × 1 Gbps Linux bonding interfaces (mode2 or mode4 is recommended) |
To deploy SeerEngine-SDWAN on a VM, make sure that VM uses VMware ESXi 6.7.0 or a higher version or H3C_CAS-E0706 or a higher version.
If superthreading is enabled, the minimum number of vCPU cores required is twice the number of CPU cores required for deployment on a physical server. If superthreading is disabled, the minimum requirements for the number of vCPU cores, memory size, and drive configuration are the same as those for deployment on a physical server.
To deploy SeerEngine-SDWAN on a VMware VM, you must enable promiscuous mode and forged transmits on the host attached to the VM.
Software requirements
SeerEngine-SDWAN runs on the Unified Platform as a component. Before deploying SeerEngine-SDWAN, first install the Unified Platform.
Table 5 CPU and operating system compatibility
|
CPU |
Operating system |
|
x86-64(Intel64/AMD64) |
H3Linux |
|
ARM |
Galaxy Kylin V10 |
The following installation packages must be deployed when you deploy the Unified Platform:
· common_PLAT_GlusterFS_2.0
· general_PLAT_portal_2.0
· general_PLAT_kernel_2.0
The following installation packages are deployed automatically when you deploy SeerEngine-SDWAN components:
· general_PLAT_kernel-base_2.0
· general_PLAT_websocket_2.0
· general_PLAT_Dashboard_2.0
· general_PLAT_widget_2.0
To deploy the general_PLAT_network_2.0 package, deploy SeerEngine-SDWAN components first.
Table 6 Installation packages
|
Installation package |
Description |
Remarks |
|
common_PLAT_GlusterFS_2.0_<version>.zip |
Provides local shared storage functionalities. |
Required |
|
general_PLAT_portal_2.0_<version>.zip |
Provides portal, unified authentication, user management, service gateway, and help center functionalities. |
Required |
|
general_PLAT_kernel_2.0_<version>.zip |
Provides access control, resource identification, license, configuration center, resource group, and log functionalities. |
Required |
|
general_PLAT_kernel-base_2.0_<version>.zip |
Provides alarm, access parameter template, monitoring template, report, email, and SMS forwarding functionalities. |
Required |
|
general_PLAT_websocket_2.0_<version>.zip |
Provides the southbound Websocket function. |
Required |
|
general_PLAT_Dashboard_2.0_<version>.zip |
Provides the dashboard framework. |
Required |
|
general_PLAT_widget_2.0_<version>.zip |
Provides dashboard widget management. |
Required |
|
general_PLAT_network_2.0_<version>.zip |
Provides basic management of network resources, network performance, network topology, and iCC. Install this application if you are to check match of the software versions with the solution. |
Optional |
Client requirements
You can access SeerEngine-SDWAN from a Web browser without installing any client. As a best practice, use Google Chrome 70 or a later version.
Pre-installation checklist
Table 7 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 |
Google Chrome 70 or a later version is installed on the client. |
|
Partitioning the system drive
Before installing SeerEngine-SDWAN, partition the system drive as described in Table 8.
Table 8 Drive partition settings
|
Mount point |
Minimum capacity |
Boot mode |
Remarks |
|
2*2.4TB, RAID 1 |
|||
|
/var/lib/docker |
500 GiB |
BIOS/UEFI |
Expansion is allowed when the drive space is sufficient. |
|
/boot |
1024 MiB |
BIOS/UEFI |
N/A |
|
swap |
1024 MiB |
BIOS/UEFI |
N/A |
|
/var/lib/ssdata |
500GiB |
BIOS /UEFI |
Expansion is allowed when the drive space is sufficient. |
|
/ |
700 GiB |
BIOS /UEFI |
Expansion is allowed when the drive space is sufficient. |
|
/boot/efi |
200 MiB |
UEFI |
N/A |
|
GFS |
500 GiB |
N/A |
You must perform a manual partitioning. To deploy other components except for the Unified Platform and SDWAN controller, determine the capacity required and then expand the drive. |
|
2*50GB, RAID 1 |
|||
|
/var/lib/etcd |
50 GiB |
BIOS /UEFI |
You must mount a separate drive. |
Deploying SeerEngine-SDWAN
This chapter describes the procedure for deploying SeerEngine-SDWAN as a component from the Unified Platform. After successful deployment, SeerEngine-SDWAN runs as a containerized application on the host where the Unified Platform is installed.
|
|
IMPORTANT: To deploy SeerEngine-SDWAN on Unified Platform in E0704 or later, you are not required to configure network settings, bind networks and subnets to the component, and confirm parameters. |
To install SeerEngine-SDWAN:
1. Log in to the Unified Platform.
See H3C Unified Platform Deployment Guide for the operation procedure.
2. On the top navigation bar, click System.
3. Click Deployment.
4. Click Install.
5. Click Upload to upload the component installation package, and then click Next.
Figure 1 Uploading the component installation package
6. Select the component to be installed (SD-WAN in this example) and the component version, and then click Next.
Figure 2 Selecting the component to install
7. Retain default parameter settings and click Next.
Figure 3 Configuring parameters
8. Create a network and add a subnet to the network. Specify the hosts on which SeerEngine-SDWAN is to be installed and specify the uplink interface used by SeerEngine-SDWAN on each host.
You can use the NIC used by the H3Linux operating system on a host for its uplink interface. If an uplink interface on a host needs to be shared by multiple networks, assign the networks to different VLANs for isolation.
If you do not use NIC sharing, enable another NIC by performing the following tasks:
a. Log in to the server where the Unified Platform is installed.
b. Edit the configuration file of a NIC, ethA09-2 in this example.
[root@node1 /]# vi /etc/sysconfig/network-scripts/ifcfg-ethA09-2
c. Change the values of BOOTPROTO and ONBOOT as shown in Figure 4.
Figure 4 Editing the configuration file of a NIC
d. Use the ifdown and ifup commands to restart the NIC.
As a best practice to avoid system failures, do not use the ifconfig command to shut down or start a NIC.
[root@node1 /]# ifdown ethA09-2
[root@node1 /]# ifup ethA09-2
e. Use the ifconfig command to verify that the NIC is in up state.
The subnet address range and address pool are used to assign IP addresses to members in the SeerEngine-SDWAN cluster. As a best practice, use Table 9 to determine the address pool size for a subnet.
Table 9 Number of IP addresses required for a subnet
|
Component |
Default cluster members |
Number of default network's IP addresses |
|
SeerEngine-SDWAN |
· Cluster mode: 3 · Standalone mode: 1 |
1 × number of cluster members |
In this example, create a MACVLAN network with a subnet containing a minimum of three IP addresses in the address pool.
|
|
IMPORTANT: If you assign the network to a VLAN, be sure to configure the corresponding VLAN settings on the device interface so outgoing packets of the host's uplink interface can carry the correct VLAN tag. |
9. Click Next.
Figure 5 Configuring network settings
10. Skip node binding and click Next.
Figure 6 Binding to nodes
11. Bind networks and subnets to SeerEngine-SDWAN, and then click Next.
Figure 7 Binding networks and subnets to components
12. Confirm parameters and then click Deploy.
The platform sets the cluster IP address for each component based on address pool configuration. To edit the cluster IP address for a component, click the IP address in the Container NIC IP column for that component. Make sure the manually specified address is within the specified subnet for the component.
Figure 8 Confirming network parameters
13. To view detailed
information about a component, click
the 
icon to the left of a component, and then click 
in
the Actions column for that component.
Figure 9 Expanding component information
14. After deployment, click Home on the top navigation bar to access the SeerEngine-SDWAN home page.
Figure 10 SeerEngine-SDWAN home page
Registering SeerEngine-SDWAN
Installing the activation file on the license server
For the activation file request and installation procedure, see H3C Software Products Remote Licensing Guide.
Obtaining licenses
1. Log in to the SeerEngine-SDWAN controller.
2. From the navigation pane, select System > License.
3. Configure the parameters for the license server as described in Table 10.
Table 10 License server parameters
|
Item |
Description |
|
IP address |
Specify the IP address configured on the license server used for internal communication in the cluster. |
|
Port number |
Specify the service port number of the license server. The default value is 5555. |
|
Username |
Specify the client username configured on the license server. |
|
Password |
Specify the client password configured on the license server. |
4. Click Connect to connect the controller to the license server.
The controller will automatically obtain licensing information after connecting to the license server.
Backing up and restoring SeerEngine-SDWAN components
For more information, see H3C Unified Platform Deployment Guide.
Upgrading the controller
|
|
CAUTION: During the upgrade process, do not perform configuration backup or restoration operations. |
The controller can be upgraded on the Unified Platform with the configuration retained.
To upgrade the controller:
1. Log in to the Unified Platform. Click System > Deployment.
Figure 11 Deployment page (1)
2. Click the left chevron button 
for the controller to
expand controller information, and then click the upgrade icon 
.
Figure 12 Deployment page (2)
3. Select the uploaded installation package, and then click Upgrade.
Figure 13 Deployment page (3)
4. View the upgrade progress.
Figure 14 Upgrade progress
5. Click OK.
Uninstalling the controller
1. Log in to the Unified Platform. Click System > Deployment.
2. Click the 
icon to the left of the controller name and then
click Uninstall.
Figure 15 Uninstalling the controller
