In the DC scenario, various component services are complicated, and hard to operate. After complicated operations, you might fail to achieve the expected results. As a result, a large number of human and material resources are wasted. Therefore, it is necessary to perform a rehearsal before deploying actual services. During the rehearsal process, you can learn and avoid risks, so that you can reduce the risk possibilities for the production environment to the maximum extent. The simulation function is introduced for this purpose. The simulation function simulates a service and estimates resource consumption before you deploy the service. It helps users to determine whether the current service orchestration can achieve the expected effect and affect existing services, and estimate the device resources to be used.

Depending on the usage scenarios, simulations include global ops topologies simulation and tenant service simulation.

Global ops topologies simulation—Builds a simulation model for firewalls or network-wide devices in the global ops topology, and performs connectivity check on the underlay of the simulation model.

Tenant service simulation—Performs a connectivity check on the overlay of the DC devices.

Installation procedure

The DTN component and the simulation hosts work together to enable simulation. Depending on the usage scenarios, including global ops topologies simulation and tenant service simulation, the DTN component installation procedure varies, as shown below.

Table 1 Installation procedure for the DTN component (convergence deployment)

Step	Task	Remarks
Prepare servers	Prepare multiple servers based on the recommended deployment scenario. Use three servers to form a cluster (deploy the DTN component on one master node). Install the simulation host on one server.	Required. For hardware and software requirements, see "Software and hardware requirements."
Obtain the installation packages	Based on the recommended simulation deployment scenario (convergence deployment of the DTN component + standalone deployment of the simulation hosts), to deploy the simulation feature (including global ops topologies simulation and tenant service simulation), first obtain the following component installation packages: DTN component, simulation host, and other supporting components.	Required. For the installation package descriptions, see "Obtain the software packages."
Plan disk partitions	Configure and partition the disks according to the requirements in the resource calculator.	Required.
Plan the network	Plan the network	Optional.
Deploy the Matrix cluster	Install the operating system and deploy the Matrix cluster on the servers. For more information, see H3C Unified Platform Deployment Guide.	Required.
Deploy Unified Platform	1. Deploy the required Base application package 2. Deploy the Common application package 3. In the tenant service simulation scenario, deploy the Connect application package. For more information, see H3C Unified Platform Deployment Guide.	Required.
Deploy the controller	After you install Unified Platform, deploy the controller on the server. For more information, see the compatible H3C SeerEngine-DC Installation Guide.	Required in the tenant service simulation scenario.
Deploy the global ops topologies	· Deploy the dependent components for the global ops topologies component, such as U-Center 5.0 and DC controller · Deploy the global ops topologies component For more information, see the compatible H3C SeerEngine-DC Global Ops Topologies Installation Guide.	Required in the global ops topologies scenario.
Deploy the DTN component (convergence deployment)	· Log in to Matrix · Upload installation packages · Select applications · Select installation packages · Configure parameters	Required.

Table 2 Installation procedure for the simulation hosts (standalone deployment)

Step	Task	Remarks
Prepare servers	Prepare multiple servers based on the recommended deployment scenario. Use three servers to form a cluster (deploy the DTN component on one master node). Install the simulation host on one server.	Required. For hardware and software requirements, see "Software and hardware requirements."
Obtain the installation packages	Based on the recommended simulation deployment scenario (convergence deployment of the DTN component + standalone deployment of the simulation hosts), to deploy the simulation feature (including global ops topologies simulation and tenant service simulation), first obtain the following component installation packages: DTN component, simulation host, and other supporting components.	Required. For the installation package descriptions, see "Obtain the software packages."
Plan disk partitions	Configure and partition the disks according to the requirements in the resource calculator.	Required.
Plan the network	Plan the network	Optional.
Deploy the operating system	Install the operating system	Required.
Deploy the DTN component (convergence deployment)	· Single simulation host scenario · Multiple simulation hosts scenario	Required.

Prepare for installation

NOTE:

DTN does not support remote disaster recovery.

Software and hardware requirements

This document uses the deployment of simulation services on a cluster-mode controller as an example.

Hardware requirements (deployment on physical server)

(Recommended.) Converged deployment of DTN component + independent deployment of simulation host

The DTN component and the controller are deployed on the same master node. The simulation host is deployed independently on a physical server.

Figure 1 Matrix cluster (DTN component converged deployment + simulation host independent deployment)

Table 3 Hardware requirements for converged deployment of the DTN component

Application name	Hardware requirements	Remarks
DTN component	CPU (cores): · x86-64 (Intel64/AMD64): 6 cores, 2.0 GHz · x86-64 (Hygon): 8 cores · ARM (Kunpeng): 16 cores · ARM (Phytium): 30 cores Memory (GB): 90 Network adapter ports · Non-bonding mode: 1 × 10 Gbps · Bonding mode: 2 × 10 Gbps	The DTN component and the controller are deployed on a master node in a converged manner. You must add the required resources to the target master node.

Application name

Hardware requirements

Remarks

DTN component

CPU (cores):

· x86-64 (Intel64/AMD64): 6 cores, 2.0 GHz

· x86-64 (Hygon): 8 cores

· ARM (Kunpeng): 16 cores

· ARM (Phytium): 30 cores

Memory (GB): 90

Network adapter ports

· Non-bonding mode: 1 × 10 Gbps

· Bonding mode: 2 × 10 Gbps

The DTN component and the controller are deployed on a master node in a converged manner. You must add the required resources to the target master node.

Table 4 Hardware requirements for independent deployment of the simulation host

Application name	Hardware requirements	Remarks
Simulation host Node quantity: n	CPU (cores): · x86-64 (Intel64/AMD64): 16 cores, 2.0 GHz or above · x86-64 (Hygon): 20 cores, 2.5 GHz or above · ARM (Kunpeng): 40 cores, 2.6 GHz or above · ARM (Phytium): 78 cores, 2.1 GHz or above Memory (GB): 128 GB or above Drives: · System drive: 600 GB or above Network adapter ports Single simulation host scenario · Non-bonding mode: 2 × 10Gbps or above · Bonding mode: 4 × 10 Gbps or above ports, each two forming a Linux bond interface. Multiple simulation hosts scenario · Non-bonding mode: 3 × 10Gbps or above · Bonding mode: 6 × 10Gbps or above, each two ports forming a Linux bond interface.	Standard configuration · Single simulation host: A maximum of 48 simulated devices can be created. (n = 1) · Multiple simulation hosts: A maximum of 48 simulated devices can be deployed on the first host, and a maximum of 60 simulated devices can be deployed on each expansion host. (n=1+(total number of simulated devices-48)/60) Network adapter port description: · Simulation management network: Used by the DTN component and the simulation hosts for communication. · Simulation service network: Used by simulated devices to exchange service information (this network adapter port is not required in single-host scenario). · Node management network: Used to log in to the simulation hosts for maintenance.
Simulation host Node quantity: n	CPU (cores): · x86-64 (Intel64/AMD64): 20 cores, 2.2 GHz or above · x86-64 (Hygon): 24 cores, 2.5 GHz or above · ARM (Kunpeng): 48 cores, 2.6 GHz or above · ARM (Phytium): 96 cores, 2.1 GHz or above Memory (GB): 256 GB or above Drives: · System drive: 600GB or above Network adapter ports Single simulation host scenario · Non-bonding mode: 2 × 10Gbps or above · Bonding mode: 4 × 10 Gbps or above ports, each two forming a Linux bond interface. Multiple simulation hosts scenario · Non-bonding mode: 3 × 10Gbps or above · Bonding mode: 6 × 10Gbps or above, each two ports forming a Linux bond interface.	High-end configuration · Single simulation host: A maximum of 112 simulated devices can be created. (n = 1) · Multiple simulation hosts: A maximum of 112 simulated devices can be deployed on the first host, and a maximum of 124 simulated devices can be deployed on each expansion host. (n=1+(total number of simulated devices-112)/124) Network adapter port description: · Simulation management network: Used by the DTN component and the simulation hosts for communication. · Simulation service network: Used by simulated devices to exchange service information (this network adapter port is not required in single-host scenario). · Node management network: Used to log in to the simulation hosts for maintenance.

Application name

Hardware requirements

Remarks

Simulation host

Node quantity: n

CPU (cores):

· x86-64 (Intel64/AMD64): 16 cores, 2.0 GHz or above

· x86-64 (Hygon): 20 cores, 2.5 GHz or above

· ARM (Kunpeng): 40 cores, 2.6 GHz or above

· ARM (Phytium): 78 cores, 2.1 GHz or above

Memory (GB): 128 GB or above

Drives:

· System drive: 600 GB or above

Network adapter ports

Single simulation host scenario

· Non-bonding mode: 2 × 10Gbps or above

· Bonding mode: 4 × 10 Gbps or above ports, each two forming a Linux bond interface.

Multiple simulation hosts scenario

· Non-bonding mode: 3 × 10Gbps or above

· Bonding mode: 6 × 10Gbps or above, each two ports forming a Linux bond interface.

Standard configuration

· Single simulation host: A maximum of 48 simulated devices can be created. (n = 1)

· Multiple simulation hosts: A maximum of 48 simulated devices can be deployed on the first host, and a maximum of 60 simulated devices can be deployed on each expansion host. (n=1+(total number of simulated devices-48)/60)

Network adapter port description:

· Simulation management network: Used by the DTN component and the simulation hosts for communication.

· Simulation service network: Used by simulated devices to exchange service information (this network adapter port is not required in single-host scenario).

· Node management network: Used to log in to the simulation hosts for maintenance.

Simulation host

Node quantity: n

CPU (cores):

· x86-64 (Intel64/AMD64): 20 cores, 2.2 GHz or above

· x86-64 (Hygon): 24 cores, 2.5 GHz or above

· ARM (Kunpeng): 48 cores, 2.6 GHz or above

· ARM (Phytium): 96 cores, 2.1 GHz or above

Memory (GB): 256 GB or above

Drives:

· System drive: 600GB or above

Network adapter ports

Single simulation host scenario

· Non-bonding mode: 2 × 10Gbps or above

· Bonding mode: 4 × 10 Gbps or above ports, each two forming a Linux bond interface.

Multiple simulation hosts scenario

· Non-bonding mode: 3 × 10Gbps or above

· Bonding mode: 6 × 10Gbps or above, each two ports forming a Linux bond interface.

High-end configuration

· Single simulation host: A maximum of 112 simulated devices can be created. (n = 1)

· Multiple simulation hosts: A maximum of 112 simulated devices can be deployed on the first host, and a maximum of 124 simulated devices can be deployed on each expansion host. (n=1+(total number of simulated devices-112)/124)

Network adapter port description:

· Simulation management network: Used by the DTN component and the simulation hosts for communication.

· Simulation service network: Used by simulated devices to exchange service information (this network adapter port is not required in single-host scenario).

· Node management network: Used to log in to the simulation hosts for maintenance.

Operating system requirements

CPU and operating system compatibility

Simulation is an independent microservice of the data center controller. Table 5 shows the CPU and operating system compatibility of the DTN component, and Table 6 shows the CPU and operating system compatibility of simulation hosts.

Table 5 CPU and operating system compatibility of the DTN component

CPU	Supported operating systems	Recommended operating system
x86-64(Intel64/AMD64)	· NingOS · Kylin V10 SP2 · TencentOS-Server-3.1	NingOS
x86-64 Hygon	· NingOS · Kylin V10 SP2 · TencentOS-Server-3.1	Kylin V10 SP2
ARM Kunpeng	· NingOS · Kylin V10 SP2 · TencentOS-Server-3.1	Kylin V10 SP2
ARM Phytium	· NingOS · Kylin V10 SP2 · TencentOS-Server-3.1	Kylin V10 SP2

Table 6 CPU and operating system compatibility of simulation hosts

Operating system name	Version number	Kernel version
NingOS	V3.1.0	5.10
Kylin	Kylin V10 SP2	4.19
TencentOS Server	TencentOS-Server-3.1	5.4.119-19.0009.54

NTP requirements

Make sure the system time has been configured. As a best practice, configure NTP for time synchronization and make sure the whole network uses the same clock source for time synchronization.

Client configuration requirements

You can access Unified Platform directly through a browser and do not need to install a client. As a best practice, use Google Chrome 96 or later.

Obtain the software packages

Based on the recommended simulation deployment scenario (convergence deployment of the DTN component + standalone deployment of the simulation hosts), to deploy the simulation feature (including global ops topologies simulation and tenant service simulation), first obtain the following software packages:

Table 7 Software installation packages and scenario descriptions for the DTN component (convergence deployment)

Component name		Remarks	Required/Optional
Operating system	--	The following operating systems are supported: NingOS Kylin TencentOS server	Required.
Matrix	UDTP_Matrix	Kubernetes-based platform that orchestrates and schedules Docker containers. On this platform, you can build Kubernetes clusters, deploy microservices, and monitor operations of systems, Docker containers, and microservices.	Required.
Unified Platform	UDTP_Base	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.
	BMP_Common	Common service component, which provides dashboard management, alarms, alarm aggregation, and alarm subscription.	Required.
	BMP_Connect	Connection service component: Provides upper- and lower-level site management, WebSocket channel management, and NETCONF channel management.	Optional in the tenant service simulation scenario.
	BMP_UCP_BasePlat_version_platform.zip	UCP base platform component. It provides core services for the U-Center public platform. It supports ETCD, ops domain menu registration, and visualization components. This ensures high availability, unified management, and visual display for platform operations.	Required for global ops topologies simulation.
	BMP_UCP_CollectPlat_version_platform.zip	UCP collection platform component. It provides core capabilities for the U-Center platform, including template management, maintenance tag management, collection platform services, unified resource management, resource discovery, and file transfer. These capabilities support scenarios such as data collection, resource integration, and efficient file distribution.
	BMP_CMDB_version_platform.zip	Configuration management database.
NSM	NSM_FCAPS-Res	Incorporates network devices and manages basic network device information.
	NSM_FCAPS-Perf	Monitors and displays the performance of network devices.
	NSM_FCAPS-Topo	Displays the network topology.
	NSM_FCAPS-ICC	Installation package for network resources
Global ops topologies	SeerEngine_Digitalmap	Provide features like visualizing the entire network in one map, pinpointing faults in seconds, and seamless third-party integration.
DC scenario	SeerEngine-DC	DC controller	Required in the tenant service simulation scenario.
DTN component	SeerEngine_DC_DTN	DC simulation component, which provides twin network management, tenant service simulation, underlay service simulation, and simulation evaluation.	Required.

Table 8 Software installation packages and scenario descriptions for the simulation hosts (standalone deployment)

Component name	Remarks	Required/Optional
Operating system	--	The following operating systems are supported: NingOS Kylin TencentOS server	Required.
Simulation host	SeerEngine_DC_DTN_HOST	A virtualization platform built based on hardware virtualization technology, which primarily hosts virtual network devices.	Required.

Component name

Remarks

Required/Optional

Operating system

The following operating systems are supported:

NingOS

Kylin

TencentOS server

Required.

Simulation host

SeerEngine_DC_DTN_HOST

A virtualization platform built based on hardware virtualization technology, which primarily hosts virtual network devices.

Required.

NOTE:

· For the hardware configuration, see the iService hardware resource calculation tool.

· The x86 and ARM installation packages for components and Unified Platform share the same functions and usage guidelines. This document uses the x86 image naming format.

· For some components, only installation packages for a single architecture (x86 or ARM) are released. See the actual released image files. Select the appropriate installation package based on the server architecture.

Verify the software packages

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

Prepare for the installation

Plan disk partitions

To configure and partition the disks, see the requirements in the resource calculator. Do not use automatic partitioning.

Plan the network

Network topology

Standalone deployment of the simulation hosts

In the standalone deployment scenario for the simulation hosts, four types of networks are involved: node management network, controller management network, simulation management network, and simulation service network.

· Node management network

The node management network is used to log in to servers for maintenance.

· Controller management network

The controller management network is used for cluster communication between controllers and for managing devices/network elements.

· Simulation management network

The simulation management network is used by the DTN component and the simulation hosts to exchange management information.

· Simulation service network

The simulation service network is used by simulated devices on simulation hosts to exchange service information.

When multiple simulation hosts exist, they communicate with each other through a switch.

When only one simulation host exists, you do not need to connect the simulation host and the switch, without requiring a network adapter port.

Before deploying the simulation feature, you must first plan the simulation management network and simulation service network.

Figure 2 Cloud data center scenario without remote disaster recovery (deploying only the DTN component with multiple simulation hosts)

Figure 3 Cloud data center scenario without remote disaster recovery (deploying only the DTN component with a single simulation host)

IMPORTANT:

· If the controller management network and simulation management network use the same management switch, you must also configure VPN instances for isolation on the management switch to prevent IP address conflicts from affecting the services. If the controller management network and simulation management network use different management switches, physically isolate these switches.

· The management IP of the simulation host and the management IPs of simulated devices must be able to reach the DTN component IP address at Layer 3. To ensure network connection stability and reliability, make sure the management IPs of simulated devices exactly match the management IPs of devices in the production environment. For more information, see "Deployment across Layer 3 networks."

· In the multiple simulation hosts scenario, on the port connecting the switch to the service interface of a simulation host, execute the port link-type trunk command to configure the link type of the port as trunk, and execute the port trunk permit vlan vlan-id-list command to assign the port to 150 continuous VLANs. Among these VLAN IDs, the first ID is the VLAN ID specified for simulation host installation, and the end VLAN ID is the start VLAN ID+149. For example, if the start VLAN ID is 11, the permitted VLAN ID range is 11 to 160. When you plan the network, do not use any VLAN ID permitted by the port.

· When the device and controller are deployed across Layer 3, the simulation host and the DTN component must be connected through a management switch.

Plan IP addresses

Standalone deployment of the simulation hosts

As a best practice, in the standalone deployment scenario for the simulation hosts, calculate the number of IP addresses for each network according to Table 9.

Table 9 Number of addresses in subnet IP address pools

Component/node name	Network name (type)	Max members in cluster	Default members in cluster	Calculation method	Remarks
DTN component	Simulation management network (MAC-VLAN)	1	1	Single node deployment, which needs only one IP	Used by the DTN component deployed on the controller
Simulation host node	Simulation management network	1 × number of simulation hosts	1 × number of simulation hosts	1 × number of simulation hosts	Used by the DTN component to incorporate hosts
	Simulation service network	1 × number of simulation hosts	1 × number of simulation hosts	1 × number of simulation hosts	Used by simulated devices to exchange service information, supporting only IPv4. In a single simulation host scenario, you do not need to plan this network.
	Node management network	1 × number of simulation hosts	1 × number of simulation hosts	1 × number of simulation hosts	Used to log in to hosts for maintenance.

Table 10 IP address planning

Component/node name	Network name (type)	IP address
DTN component	Simulation management network (MAC-VLAN)	Subnet address: 192.168.12.0/24 (the gateway address is 192.168.12.1)
DTN component	Simulation management network (MAC-VLAN)	Network address pool: 192.168.12.133/24 to 192.168.12.164/24 (gateway address: 192.168.12.1)
Simulation host node	Simulation management network	Network address pool: 192.168.12.165/24 to 192.168.12.175/24 (gateway address: 192.168.12.1)
	Simulation service network	Network address pool: 192.168.11.134/24 to 192.168.11.144/24 (gateway address: 192.168.11.1)
	Node management network	Network address pool: 192.168.10.110/24 to 192.168.10.120/24 (gateway address: 192.168.10.1)

NOTE:

The simulation management network, simulation service network, and node management network must be on different network segments.

Deploy the DTN component (convergence deployment)

Deploy Unified Platform before deploying the DTN component. Then, deploy the DTN component on the Matrix convergence deployment page.

Install Unified Platform

For information about installing Unified Platform, see H3C Unified Platform Deployment Guide.

Log in to Matrix

NOTE:

Deploying the DTN component on the Matrix convergence deployment page is supported in Unified Platform E0722 and later versions.

1. In the address bar of a browser, enter the login address of Matrix:

a. If an IPv4 address is used, access https://ip_address:8443/matrix/ui, for example, https://172.16.101.200:8443/matrix/ui. The following configuration in this document uses IPv4.

b. If an IPv6 address is used, access https://[ip_address]:8443/matrix/ui, for example, https://[2000::100:611]:8443/matrix/ui.

ip_address represents the IP address of the node, and 8443 is the default port number.

2. On the top navigation bar, click DEPLOY. From the navigation pane, select Convergence Deployment.

Figure 4 Convergence Deployment

Upload installation packages

1. Obtain the DTN installation package. The package name is as shown in Table 11, where version represents the version number. Select an installation package based on the server architecture.

Table 11 Installation package name

Component name	Component installation package name	Remarks
DTN	· x86: SeerEngine_DC_DTN-version.zip · ARM: SeerEngine_DC_DTN-version-ARM64.zip	Used for the simulation feature.

Component name

Component installation package name

Remarks

DTN

· x86: SeerEngine_DC_DTN-version.zip

· ARM: SeerEngine_DC_DTN-version-ARM64.zip

Used for the simulation feature.

2. Click Packages Management to access the installation package management page.

Figure 5 Installation package management

3. Click Upload. In the dialog box that opens, click Select Files, and select component installation packages. Then, click Upload to upload the selected component installation packages to the system.

Figure 6 Upload or register the installation package

4. After the installation package is uploaded, click Return on the installation package management page to return to the convergence deployment page.

Select applications

1. On the convergence deployment page, click Install to access the application selection page.

2. Select the DTN component.

Figure 7 Select the DTN component

3. Click Next.

Select installation packages

1. On the installation package selection page, the latest version of the installation package is displayed by default. You can select an installation package version from the list.

Figure 8 Select installation packages

2. After selecting the installation package, click Next to configure resources.

Configure resources

The DTN component does not require resource configuration. Click Next to configure parameters.

Figure 9 Configure resources

Configure parameters

Configure networks

1. Access the Network Configuration page, click Create Network, and configure the network name in the window that opens. The network type is MACVLAN by default.

2. In the subnets area, click Create. In the window that opens, configure a separate MACVLAN network for the DTN component, which must contain at least one IP address in the subnet pool.

3. In the hosts area, click Create to associate a host and uplink port for the DTN component.

IMPORTANT:

You can select only one host. Make sure the host has sufficient CPU and memory resources to ensure the stable operation of the DTN component.

Figure 10 Associate host and uplink port

4. Click OK to complete the DTN network creation.

5. Click Next to access the node binding page.

Bind nodes

1. On the DTN tab, click Select Node, and then select node, network, and subnet.

2. Click OK to complete the binding operation.

3. Click Next to access the node information verification page.

Verifying the node information

1. On the node information confirm page, you can view the planned network information for the DTN component.

2. To edit the settings, click Previous to return to the node binding page.

3. After you confirm the parameters, click Deploy. In the parameter confirmation window that opens, confirm the dependent middleware nodes and the applications to be deployed.

Figure 11 Confirm parameters

4. Click OK to start deploying the DTN component. The page will display the deployment progress.

Figure 12 Deploying component

Deploy the simulation hosts (standalone deployment)

Install the operating system

NOTE:

· The simulation host relies on the system virtualization capabilities. Make sure you select the virtualization capability when selecting the software.

· As a best practice to enhance system stability, use the recommended device types and file system types for partitioned devices.

· Installing the operating system on a server that already has an operating system installed replaces the existing operating system. To avoid data loss, back up data before you install the operating system.

NingOS operating system

Installing the operating system

The NingOS-V3-1.0.2403-x86_64-dvd.iso image is the installation image of the NingOS operating system. This section describes the procedure for installing the NingOS operating system on a server without an operating system installed.

1. After the ISO image is loaded, access the page for selecting a language.

2. Select a language (English (United States) in this example), and then click Continue.

Figure 13 Select a language

3. In the localization area, click Date and Time to set the system date and time. Select Asia as the region, Shanghai as the city, and then click Finish to return to the installation information summary page.

Figure 14 Set the date and time for the system

4. Click the Keyboard link in the LOCALIZATION area. On the page that opens, set the keyboard layout to English (US).

Figure 15 Select a keyboard layout

5. For the Software Selection option in the SOFTWARE area, Virtualization Host is selected for the base environment by default, as shown in the following figure.

Figure 16 Virtualization host selected for base environment by default

6. Click the Installation Destination link in the SYSTEM area to access the INSTALLATION DESTINATION page. Select the destination disk in the Local Standard Disks area, and select the Custom option in the Storage Configuration area. Then, click Done to access the MANUAL PARTITIONING page.

Figure 17 Installation destination page

7. In the New mount points will use the following partitioning scheme list, select the standard partition scheme, and then click Click here to create them automatically.

Figure 18 Select a partitioning scheme

8. Configure partitions as described in the following table. The /boot/efi partition exists only when the server is enabled with the UEFI functionality to install the system (if this partition does not exist, you do not need to add it manually).

Table 12 Created disk partitions

Mount point	Capacity	Applicable mode	File system	Remarks
/home	1024 MiB	BIOS mode, UEFI mode	ext4	Not less than 1024 MiB.
/boot	1024 MiB	BIOS mode, UEFI mode	ext4	Not less than 1024 MiB.
swap	1024 MiB	BIOS mode, UEFI mode	swap	Not less than 1024 MiB.
/	500 GiB	BIOS mode, UEFI mode	ext4	Configure as much capacity as possible.
/boot/efi	200 MiB	UEFI mode	EFI System Partition	Not less than 200 MiB.

9. Click Done. If the following message is displayed, create a BIOS Boot partition of 1 MiB. If no prompt message is displayed, you can skip this step.

Figure 19 Prompt for creating the BIOS Boot partition

10. The SUMMARY OF CHANGES window will open, as shown in the following figure. Click Accept Changes to return to the INSTALLATION SUMMARY page.

Figure 20 Summary of changes

11. Select the administrator account settings. Use either the root or admin user as the administrator account.

12. To use the root user as the administrator account:

¡ Click the Root Account link in the USER SETTINGS area to configure the root user as the administrator account.

¡ Select the Enable Root Account option and set the root user password. Then, click Done to return to the INSTALLATION SUMMARY page.

Figure 21 Set the root account

¡ If you use the root user as the administrator account, the user has privileges of all operations, and the admin user will not be created.

Figure 22 Use the root user as the administrator account

¡ To use the admin user as the administrator account:

- When using the admin user as the administrator account, you must also set the root password. You must first set the root password and then create the admin user. If you do not do that, the SSH permissions of the root user will be disabled.

- In the user settings area, click the create user link. Select the Add administrative privileges to this user account (wheel group membership) option to make the account an administrator.

- As shown in the following figure, set the admin user password. Then, click Done to return to the INSTALLATION SUMMARY page.

Figure 23 Create the admin user

Figure 24 The admin user is created

13. Click the Network & Host Name link in the SYSTEM area to access the NETWORK & HOST NAME page.

14. As shown in the following figure, enter the host name in the Host Name field and then click Apply.

Figure 25 Network & host name page

15. On the network and host name configuration page, you can configure the network card. NIC bonding allows you to bind multiple NICs to form a logical NIC for NIC redundancy, bandwidth expansion, and load balancing.

If you do not configure NIC bonding, click Configure and configure the NIC in the window that opens. On the General tab, select the Connect automatically with priority option, and keep the All users may connect to this network option selected, as shown in the following figure.

NOTE:

Configure network ports as planned.

· The network port IP for the simulation management network is used for communication with the DTN component.

· The network port IP for the simulated device service network is used for service communication between simulated devices. Specify this IP address in the installation script in "Configure simulation hosts." You do not need to specify this IP address in this section.

· The network port IP for the node management network is used for routine maintenance of servers.

Figure 26 General tab

16. The host supports dual protocol stacks.

¡ To configure an IPv4 address, click the IPv4 Settings tab, select Manual from the Method list, click Add in the addresses area, and configure the simulation management IPv4 address for the simulation host. After configuration is complete, click Save.

Figure 27 Configure the server IPv4 address

¡ To configure only IPv6 address, click the IPv4 Settings tab, select Disabled from the Method list. Then, click the IPv6 Settings tab, select Manual from the Method list, click Add in the addresses area, configure the simulation management IPv6 address for the simulation host. After configuration is complete, click Save.

¡ In a dual-stack environment, configure both IPv4 and IPv6 addresses.

NOTE:

· Before you configure an IPv6 address in the IPv6 single-stack environment, you must disable the IPv4 address that has been configured.

· After you complete operating system installation, use the nmcli connection reload and nmcli connection up commands to restart the NICs.

17. After you configure the network, manually enable the specified NICs. Click Done to return to the INSTALLATION SUMMARY page.

Figure 28 Enable network card

18. Repeat steps (14) and (16) to configure node management IP addresses for other simulation hosts (network address pool: 192.168.10.110 to 192.168.10.120, taking 192.168.10.110 as an example).

19. Click Begin Installation to start installing the operating system.

20. After installation is completed, the server will automatically restart. The screen after restart is as shown in the following figure.

Figure 29 Installation completed

Configure simulation hosts

IMPORTANT:

· Executing the uninstallation script will restart the network service and tear down the SSH connection. To avoid service interruption, perform the operations through the remote console of the server/VM.

· Configure the following settings on each simulation host.

· If you select a non-root user as the login user or the root user is disabled, add sudo before every command.

Single simulation host scenario

When only one simulation host is deployed, the simulation service network does not require a network port because communication between simulated devices occurs within the host. The deployment method is as follows:

1. Obtain the SeerEngine_DC_DTN_HOST installation package, upload it to the server, and decompress it. The installation package name is SeerEngine_DC_DTN_HOST-version.zip (version is the software version number). This example uses software version E7101.

[root@host01 root]# unzip SeerEngine_DC_DTN_HOST-E7101.zip

2. Execute the chmod command to assign permissions to the user.

[root@host01 root]# chmod +x -R SeerEngine_DC_DTN_HOST-E7101

3. Enter the SeerEngine_DC_DTN_HOST-version/ directory decompressed from the SeerEngine_DC_DTN_HOST installation package and use the ./install.sh management_nic command to install the package. This command uses 3.0.0.3/16 as the service address for simulated devices. If this address conflicts with the network plan, you can execute the ./install.sh management_nic service_cidr command to perform the installation with a service address specified.

Parameters:

management_nic: Name of the simulation management network adapter port.

service_cidr: Inter-simulated device communication address.

Use the default address 3.0.0.3/16 as the service address to install the simulation host:

[root@host01 SeerEngine_DC_DTN_HOST-E7101]# ./install.sh ens1f0

Installing ...cd

check network service ok.

check libvirtd service ok.

check management bridge ok.

check sendip ok.

check vlan interface ok.

Complete!

Specify a specific address (taking 192.168.11.134/24 as an example) to install the simulation host:

[root@host01 SeerEngine_DC_DTN_HOST-E7101]# ./install.sh ens1f0 192.168.11.134/24

Installing ...cd

check network service ok.

check libvirtd service ok.

check management bridge ok.

check sendip ok.

check vlan interface ok.

Complete!

NOTE:

· service_cidr represents the inter-simulated device communication address. The connection between the devices is implemented through a UDP tunnel by using this IP.

· The system's default restart timeout for network service is five minutes. After the simulation host is deployed, the system will automatically change the restart timeout for network service to 15 minutes.

· After completing the configuration of the simulation host, if you edit the host name, make sure the new host name also exists in the /etc/hosts domain name resolution file. If the host name does not exist in the file, add it manually.

Multiple simulation hosts scenario

To deploy multiple simulation hosts, the simulation service network requires a network port to ensure successful communication between simulated devices. The deployment method is as follows.

[root@host01 root]# unzip SeerEngine_DC_DTN_HOST-E7101.zip

2. Execute the chmod command to assign permissions to the user.

[root@host01 root]# chmod +x -R SeerEngine_DC_DTN_HOST-E7101

3. Enter the SeerEngine_DC_DTN_HOST-version/ directory decompressed from the SeerEngine_DC_DTN_HOST installation package and use the ./install.sh management_nic service_nic vlan_start service_cidr command to perform the installation.

Parameters:

management_nic: Name of the simulation management network adapter port.

service_nic: Name of the simulation service network adapter port.

vlan_start: Start VLAN ID.

service_cidr: Inter-simulated device communication address.

[root@host01 SeerEngine_DC_DTN_HOST-E7101]# ./install.sh ens1f0 ens1f1 11 192.168.11.134/24

Installing ...cd

check network service ok.

check libvirtd service ok.

check management bridge ok.

check sendip ok.

check vlan interface ok.

Complete!

NOTE:

· The VLAN range is [vlan_start, vlan_start+149], and all hosts must be consistent. Based on the VLAN, 150 VLAN subinterfaces will be created for the simulation network ports to facilitate inter-host communication.

· If the script execution prompts "NIC {service_NIC_name} does not support 150 VLAN subinterfaces. Please select another service NIC for simulation," it indicates that the currently selected network port does not support configuring 150 VLAN subinterfaces. You need to select another service network port for the simulation.

· service_cidr represents the communication address for inter-simulated devices. Device connections are established through a UDP tunnel, which will use this IP. Make sure the CIDR for multiple simulation hosts is in the same subnet.

· The system's default network service restart timeout is 5 minutes. After the deployment of the simulation hosts, the system will automatically change the network service restart timeout to 15 minutes.

· After completing the configuration of the simulation hosts, if you have modified the host name, make sure the new hostname is also present in the /etc/hosts domain name resolution file. If the host name does not exist in the file, add it manually.

Deployment across Layer 3 networks

Network description

In this chapter, the controller management network, node management network, simulation management network, and simulated device service network share one switch to deploy the Layer 3 management networks for simulation.

NOTE:

This section describes the deployment of simulation device hosts on physical servers as an example. The deployment method for integrated simulation device hosts is consistent with that of standalone simulation device hosts. See the actual network configuration for specific details.

Figure 30 Management network diagram

Table 13 IP planning for the simulation management network

Component/node name	IP address plan	Interfaces
DTN component	IP address: 192.168.15.133/24 (gateway address: 192.168.10.1)	Ten-GigabitEthernet1/0/25, VLAN 40
Simulation host 1	IP address: 192.168.12.134/24 (gateway address: 192.168.12.1, NIC: ens1f0)	Ten-GigabitEthernet1/0/26, VLAN 40
Simulation host 2	IP address: 192.168.12.135/24 (gateway address: 192.168.12.1, NIC: ens1f0)	Ten-GigabitEthernet1/0/27, VLAN 40
Simulated device 1	IP address: 192.168.20.136/24 (gateway address: 192.168.21.1)
Simulated device 2	IP address: 192.168.20.137/24 (gateway address: 192.168.10.1)
Simulated device 3	IP address: 192.168.21.134/24 (gateway address: 192.168.21.1)
Simulated device 4	IP address: 192.168.21.135/24 (gateway address: 192.168.21.1)
IPv4 Management Network Address Pool	IP address: 2.0.0.0/22 (gateway address: 2.0.0.1)

NOTE:

In the Layer 3 management network, use the management network address pool (for IPv6 management networks, the IPv6 management network address pool is required). The configuration of the management network address pool can be performed by following these steps: Log in to the controller, navigate to the Automation > Data Center Network > Simulation > Build Simulation Network page, click Simulation Network Pre-configuration, select the parameter settings tab, and configure the corresponding management network address pool in the address pool information section.

Table 14 Simulated device service network address planning

Component/node name	IP address plan	Interfaces
Simulation host 1	IP address: 192.168.11.134/24 (gateway address: 192.168.12.1, NIC: ens1f1)	Ten-GigabitEthernet1/0/28, VLAN 30
Simulation host 2	IP address: 192.168.11.135/24 (gateway address: 192.168.12.1, NIC: ens1f1)	Ten-GigabitEthernet1/0/29, VLAN 30

Table 15 IP planning for the node management network

Component/node name	IP address plan	Interfaces
Controller	IP address: 192.168.10.110/24 (gateway address: 192.168.10.1)	Ten-GigabitEthernet1/0/21, VLAN 10
DTN component	IP address: 192.168.10.111/24 (gateway address: 192.168.10.1)	Ten-GigabitEthernet1/0/22, VLAN 10
Simulation host 1	IP address: 192.168.10.112/24 (gateway address: 192.168.10.1)	Ten-GigabitEthernet1/0/23, VLAN 10
Simulation host 2	IP address: 192.168.10.113/24 (gateway address: 192.168.10.1)	Ten-GigabitEthernet1/0/24, VLAN 10

Configuration example

In the simulation environment, the interfaces that connect the management switch to the same type of network of the DTN component and different simulation hosts must belong to the same VLAN. More specifically, the interfaces that connect to the simulation management network belong to VLAN 40, the interfaces that connect to the simulated device service network belong to VLAN 30, and the interfaces that connect to the node management network belong to VLAN 10.

Perform the following tasks on the management switch:

1. Create VLANs 40, 30, and 10 for the simulation management network, simulated device service network, and node management network, respectively.

[device] vlan 40

[device-vlan40] quit

[device] vlan 30

[device-vlan30] quit

[device] vlan 10

[device-vlan10] quit

2. Assign to VLAN 40 the interface connecting the management switch to the simulation management network of the DTN component, Ten-GigabitEthernet 1/0/25 in this example. Assign to VLAN 10 the interface connecting the management switch to the node management network of the DTN component, Ten-GigabitEthernet 1/0/22 in this example.

[device] interface Ten-GigabitEthernet1/0/25

[device-Ten-GigabitEthernet1/0/25] port link-mode bridge

[device-Ten-GigabitEthernet1/0/25] port access vlan 40

[device-Ten-GigabitEthernet1/0/25] quit

[device] interface Ten-GigabitEthernet1/0/22

[device-Ten-GigabitEthernet1/0/22] port link-mode bridge

[device-Ten-GigabitEthernet1/0/22] port access vlan 10

[device-Ten-GigabitEthernet1/0/22] quit

3. Assign the interface (Ten-GigabitEthernet 1/0/26 in this example) connecting the management switch to the simulation management network of simulation host 1 to VLAN 40. Assign the interface (Ten-GigabitEthernet 1/0/28 in this example) connecting the management switch to the simulation service network of simulation host 1 to VLAN 30. Assign the interface (Ten-GigabitEthernet 1/0/23 in this example) connecting the management switch to the node management network of simulation host 1 to VLAN 10.

[device] interface Ten-GigabitEthernet1/0/26

[device-Ten-GigabitEthernet1/0/26] port link-mode bridge

[device-Ten-GigabitEthernet1/0/26] port access vlan 40

[device-Ten-GigabitEthernet1/0/26] quit

[device] interface Ten-GigabitEthernet1/0/28

[device-Ten-GigabitEthernet1/0/28] port link-mode bridge

[device-Ten-GigabitEthernet1/0/28] port access vlan 30

[device-Ten-GigabitEthernet1/0/28] quit

[device] interface Ten-GigabitEthernet1/0/23

[device-Ten-GigabitEthernet1/0/23] port link-mode bridge

[device-Ten-GigabitEthernet1/0/23] port access vlan 10

[device-Ten-GigabitEthernet1/0/23] quit

4. Assign the interface (Ten-GigabitEthernet 1/0/27 in this example) connecting the management switch to the simulation management network of simulation host 2 to VLAN 40. Assign the interface (Ten-GigabitEthernet 1/0/29 in this example) connecting the management switch to the simulation service network of simulation host 2 to VLAN 30. Assign the interface (Ten-GigabitEthernet 1/0/24 in this example) connecting the management switch to the node management network of simulation host 2 to VLAN 10.

[device] interface Ten-GigabitEthernet1/0/27

[device-Ten-GigabitEthernet1/0/27] port link-mode bridge

[device-Ten-GigabitEthernet1/0/27] port access vlan 40

[device-Ten-GigabitEthernet1/0/27] quit

[device] interface Ten-GigabitEthernet1/0/29

[device-Ten-GigabitEthernet1/0/29] port link-mode bridge

[device-Ten-GigabitEthernet1/0/29] port access vlan 30

[device-Ten-GigabitEthernet1/0/29] quit

[device] interface Ten-GigabitEthernet1/0/24

[device-Ten-GigabitEthernet1/0/24] port link-mode bridge

[device-Ten-GigabitEthernet1/0/24] port access vlan 10

[device-Ten-GigabitEthernet1/0/24] quit

5. Create a VPN instance.

[device] ip vpn-instance simulation

[device-vpn-instance-simulation] quit

6. Create a VLAN interface, and bind it to the VPN instance. Assign all gateway IP addresses to the VLAN.

[device] interface Vlan-interface40

[device-Vlan-interface40] ip binding vpn-instance simulation

[device-Vlan-interface40] ip address 192.168.12.1 255.255.255.0

[device-Vlan-interface40] ip address 192.168.15.1 255.255.255.0 sub

[device-Vlan-interface40] ip address 192.168.20.1 255.255.255.0 sub

[device-Vlan-interface40] ip address 192.168.21.1 255.255.255.0 sub

[device-Vlan-interface40] ip address 2.0.0.1 255.255.255.0 sub

[device-Vlan-interface40] quit

IMPORTANT:

· When production physical devices use dynamic routing protocols (including but not limited to OSPF, IS-IS, BGP) to advertise management IP routes, the VLAN interface (VLAN 40) must be configured with the same routing protocol.

· When the management port of a production physical device is of the loopback type and the subnet mask length of the management IPv4 address is 32, configure the gateway IP on the management switch according to Class A (8-bit mask), Class B (16-bit mask), or Class C (24-bit mask) addressing.

· When production physical devices use OSPF to advertise management IP routes, the VLAN interface (VLAN 40) must be configured with the ospf peer sub-address enable command.

7. When the simulation network uses the License Server of the controller, taking the license server deployed in the controller as an example, you need to configure the following static routes on the managed device. In this example, 192.168.10.110 is the IP of the server where the license server is located, and 192.168.15.133 is the IP of the DTN component.

[device] ip route-static vpn-instance simulation 192.168.10.110 32 192.168.15.133

When the management networks of the simulation hosts and the DTN component are deployed across Layer 3, the following configuration must be performed on simulation host 1 and simulation host 2.

8. Add the static route to the DTN component management network.

[root@host01 ~]# route add -host 192.168.15.133 gw 192.168.12.1

9. Make the static route to the DTN component management network persistent.

[root@host01 ~]# cd /etc/sysconfig/network-scripts/

[root@host01 network-scripts]# vi route-mge_bridge

Enter 192.168.15.133/32 via 192.168.12.1 in the file, then save and exit.

[root@host01 network-scripts]# cat route-mge_bridge

192.168.15.133/32 via 192.168.12.1

Configure basic services for the global ops topologies simulation

NOTE:

Make sure the global ops topologies and DTN components have been deployed.

Access the simulation page

1. Navigate to the Monitor > Global Ops Topologies > Global Topology page.

2. Click the Data Center icon, and select Simulation from the list. The default global ops topologies simulation page opens.

Figure 31 Simulation menu

Preconfigure the global ops topologies simulation

Configure parameter settings

1. Click the Parameters tab. The parameter settings page opens.

2. Select a simulation data source.

Table 16 Simulation data source

Parameter	Description
Simulation Data Source	You can build a simulation network based on either online or offline data. · Online Data—Collect data from the current production network to build a simulation network. During the building process, make sure all devices in the production environment are active and the inter-device links are normal. · Offline Data—Import device configuration files and link information files to build a simulation network based on offline data.

Parameter

Description

Simulation Data Source

You can build a simulation network based on either online or offline data.

· Online Data—Collect data from the current production network to build a simulation network. During the building process, make sure all devices in the production environment are active and the inter-device links are normal.

· Offline Data—Import device configuration files and link information files to build a simulation network based on offline data.

¡ Select online data. You do not need to configure other parameters in the basic information area.

¡ Select offline data: After you select Offline Data for the simulation data source, configure the relevant parameters on the Device Info tab and the Link Info tab. You can bulk import information through a configuration template.

Figure 32 Select offline data

3. View or edit the UDP port, address pool, and license settings. The address pools configured here are exclusively used by the simulation network. Make sure they do not conflict with the underlay address pools configured in the production mode.

Figure 33 Configure the UDP port, address pool, and license settings

4. Click OK.

Manage simulation images

1. Click the Manage Simulation Images tab. The simulation image management page opens.

Click Upload Image. In the dialog box that opens, select the type of the image to be uploaded, select an image of the corresponding type, and then click Upload.

The simulated device models correspond to physical devices as follows:

¡ The V9850_256H model corresponds to the S9850-4C, S9820-64H, S9820-8C, S7500X, S10500X, and S12500G-AF switch series.

¡ The V6850_56HF model corresponds to the S6805, S6825, and S6850 switch series.

¡ The V12600G model corresponds to the S12600G and S10600X switch series.

¡ The V7800XPG model corresponds to the S7800XPG, S7800-54QF, and S9600XP switch series.

¡ The vFW1000 model corresponds to the H3C and third-party firewalls.

¡ The UniCloud_vFW1000 model corresponds to the UNIS firewalls.

Figure 34 Upload an image

Figure 35 Image uploaded

Manage simulation device hosts

1. Click the Manage Simulation Device Hosts tab to access the simulation device host management page.

2. Click Add. In the dialog box that opens, configure the host name, IP address, and other parameters, and click OK.

Figure 36 Add a simulation device host

Figure 37 Simulation device host added

3. After you add the simulation device host, you can view basic information of the host on the host list, or click the icon in the Actions column for the host to view its details.

Figure 38 View detailed information about a host

Add simulation tasks and baselines

Add a baseline

1. Click the Baseline Management tab.

2. Click Add. In the dialog box that opens, specify a baseline name and select a mode.

Table 17 Mode parameters

Parameter	Description
Mode	Options include Broadcast Probe and DPV Probe. The default is Broadcast Probe. As a best practice, select Broadcast Probe if you simulate only firewalls. As a best practice, select DPV Probe if you simulate network-wide devices.

Parameter

Description

Mode

Options include Broadcast Probe and DPV Probe. The default is Broadcast Probe.

As a best practice, select Broadcast Probe if you simulate only firewalls.

As a best practice, select DPV Probe if you simulate network-wide devices.

Figure 39 Add a baseline

3. Click OK.

Configure access relationships

You can bulk import and manually add access relationships.

Bulk import access relationships

1. Access the Baseline Management page, and click Import Access Relationships. The Import Access Relationships dialog box opens.

Figure 40 Import access relationships (1)

2. Click Download Template to download the template (an excel file) to the local disk.

3. After you configure the template, drag the template to the dialog box or click Select File to select the template. Click Upload to upload the template file to the server. To reselect a template file, click Select File.

Figure 41 Import access relationships (2)

4. Click Import. The import result window automatically opens and displays the number of entries successfully imported, number of entries failing to be imported, and the import failure causes.

5. The entries successfully imported will be displayed in the access relationship list of the related baselines.

Manually add an access relationship

1. Click the icon in the Access Relationships column.

2. Click Add. In the dialog box that opens, add an access relationship. Click OK.

Figure 42 Add an access relationship (broadcast probe)

Figure 43 Add an access relationship (DPV probe)

3. To bulk delete access relationships, select one or more access relationships to be deleted, and then click the Delete button above the list.

4. You can view the details of, edit, or delete access relationships.

Add a simulation task

1. On the task management page, click Add, and then specify the device in the dialog box that opens. Click OK.

Figure 44 Add a task

2. You can edit or delete the specified tasks.

3. Click the icon in the Actions column for a task or click the name of a task to access the model building page and start simulation. The icon will be displayed for a simulation task in simulating status.

Figure 45 Task management > Simulating

Start simulation

Build a simulation model

About this feature

The system supports using H3C vFW images to accurately replicate network devices and link data from the production environment into the simulation network model.

Parse configuration

1. After you complete basic configurations for tasks, baselines, and simulation hosts, access the task management page.

2. Click the icon in the Actions column for a task or click the name of a task to access the Parse Configuration page by default.

3. Click the Parse Configuration link to start parsing the data synchronized from the production environment to the simulation environment.

NOTE: To avoid disrupting the data parsing process, do not switch pages during the data parsing process.

Table 18 Parsing rules

Scenario	Parsing rules
Offline scenario	Make sure the management IP in the physical device or context configuration file matches the IP added in the device information. If you cannot do that, the system will consider the physical device or context invalid and skip it during resolution.
Online scenario	· If the configuration cluster of a context includes the allocate interface configuration, the context is considered valid. If not, the system automatically skips the context during resolution. · The system parses the context management IP based on the security-zone name Management command. If the security-zone name Management command configuration cluster contains valid interfaces and a bound interface has a valid IP, the system recognizes the IP as the management IP. If not, the system will skip the context during parsing.

Scenario

Parsing rules

Offline scenario

Make sure the management IP in the physical device or context configuration file matches the IP added in the device information. If you cannot do that, the system will consider the physical device or context invalid and skip it during resolution.

Online scenario

· If the configuration cluster of a context includes the allocate interface configuration, the context is considered valid. If not, the system automatically skips the context during resolution.

· The system parses the context management IP based on the security-zone name Management command. If the security-zone name Management command configuration cluster contains valid interfaces and a bound interface has a valid IP, the system recognizes the IP as the management IP. If not, the system will skip the context during parsing.

Figure 46 Configuration parsing

Because the number of interfaces supported on a virtual device is limited, if the number of actually used interfaces on a device in production mode exceeds the threshold, an error message is displayed during configuration parsing for the device. Additionally, the device will be excluded from the subsequent simulation model building:

¡ Firewall: When parsing the configuration of a specific firewall, the system automatically excludes the interfaces with the shutdown command executed, the interfaces with the description command executed, and the interfaces with both the lldp enable and lldp tlv-enable basic-tlv all commands executed. After the specific interfaces are excluded, the number of actually used interfaces still exceeds 25.

¡ Switch: When the number of actually used interfaces on a switching device exceeds 58.

Configuration conversion or changes might fail on a device if the device meets any of the following conditions:

¡ The device configuration does not comply with the network standards.

¡ The IP or mask format does not comply with the IPv4 or IPv6 standards.

¡ A VLAN ID is not in the range of 1 to 4095.

¡ A port number is not in the range of 0 to 65535.

¡ An interface name does not comply with the interface naming rules for simulated devices.

¡ Change the configuration on an excluded interface.

4. After data is parsed, the page will display device information and the inter-device links. The State column displays Parsed and the Built At column displays --.

Figure 47 Model parsing completed

5. Right-click the specified device to perform the following tasks:

¡ Configuration Check—In the dialog box that opens, view detailed information about production configuration and simulation configuration.

Figure 48 Check configuration

¡ Export configuration (simulated device configuration)—Export the configuration file of the current simulated device.

6. To clear the parsed data after the configuration is parsed and before you build the model, click Clear Parsed Data. After the parsed data is cleared successfully, you must re-parse the data again. In this case, the simulation system will re-pull the device data for the specified task from the production mode.

7. Click Build Model to start building the simulation model. A dialog box will open to display the progress and percentage. After the simulation model is built, the topology will be displayed on this page. The status displays Built, and the building time is displayed.

8. After the model is built, click Delete Model to delete the current built model.

9. Click Next to access the baseline settings page.

Configure baselines

About this feature

When you generate baseline results, the system performs a connectivity check on the data synchronized from the production environment and then generates the final baseline results. You can use the baseline results as a reference standard for the current network state. During subsequent service change simulations, you can compare the baseline results with the simulation data after change to support feasibility assessments and risk identification for network changes.

Access relationship baseline

· Create an access relationship baseline

You can create an access relationship baseline through manual configuration or system recommendation. Select the creation scenario based on whether to include only simulated firewalls.

¡ Manually specify a baseline: On the Access Relationship Baselines tab, click Add. In the dialog box that opens, select the baselines for which you want to build a simulation model. Click OK.

Figure 49 Add a baseline

¡ System-recommended baseline: On the Access Relationship Baselines tab, click Generate Recommended Baseline. The system will parse the configuration of the selected firewalls and intelligently generate an access relationship baseline, which simplifies the configuration process.

CAUTION:

The system automatically generates recommended baselines only for simulated firewalls. This feature is unavailable when a physical device exists or no firewall exists.

· Generate baseline results

After the baseline is created, click Generate Baseline Results on the Access Relationship Baselines page. The system will automatically start the simulation evaluation process. The evaluation process checks connectivity for the current baseline configuration and generates a baseline evaluation result. You can compare this result with the service change simulation results later.

Figure 50 Generate baseline results

· View the check results

After the evaluation completes, follow these steps to view baseline check results and details of access relationships:

a. After the evaluation completes, click the dropdown list to the left of the access relationship baseline to view the check results. This helps you visually understand the connectivity evaluation status of the current baseline.

Figure 51 Check result

b. Click the icon. In the dialog box that opens, you can view detailed check information in the underlay network diagram to locate potential issues.

Figure 52 View the check results

c. Click the icon in the Actions column for an access relationship to view detailed information in the dialog box that opens. This helps you analyze specific access rules and their evaluation results.

Figure 53 View access relationship details

Change services

Select a baseline to build a simulation model based on the specified baseline and access relationships. You can edit the device configuration and evaluate simulation after making changes. You can change services in topology view or list view.

NOTE:

Physical firewalls cannot be edited or exported.

Edit configuration

Access the service changes page. In the configuration editing step, you can perform the following operations.

Service change steps in topology view

· Right-click the specified device or physical firewall to perform the following operations:

Figure 54 Right-click the physical wall

· Select Edit Configuration. In the dialog box that opens, edit the configuration snippet.

CAUTION:

· When you deploy a configuration snippet, it overwrites the existing configuration. Only the configuration from the most recent modification is deployed. Please ensure the integrity of the current configuration snippet.

· To successfully deploy the configuration, do not edit the username or password of the device.

· You cannot edit the configurations of interfaces whose configurations are not converted or interfaces that are not selected by the user.

Figure 55 Edit the configuration snippet

· Select Export Configuration (Production device configuration) to directly export the configuration file of the selected device.

Service change steps in list view

Click the dropdown box icon on the left of the specified device or physical firewall to view the vFW information under that physical firewall. In the Actions column for a vFW, you can perform the following tasks:

a. Click . In the dialog box that opens, edit the device configuration

b. Click to export the configuration file of the specified device to your local host.

Figure 56 Services to be deployed

Deploy configuration

1. On the Services Changes > Deploy Configuration page, view the name, management IP, vendor, status, and other information of a device.

2. After you select the specified configuration, click Deploy Configuration to deploy the edited configuration snippet to the target device.

Figure 57 Deploy configuration

Start simulation evaluation

1. After you complete service changes, click Next to open the confirmation dialog box for simulation evaluation.

2. Click OK to start simulation evaluation.

3. After simulation is completed, click OK to automatically access the simulation evaluation page.

NOTE:

· The simulation evaluation progress will be displayed during the simulation evaluation.

· If the simulated devices are security devices, the simulation evaluation process includes only checking the baseline access relationship.

· If the simulated devices are network-wide devices, the simulation evaluation process includes initializing the data model, checking the baseline access relationship, diagnosing abnormal connection status, and analyzing abnormal routes.

· During the simulation evaluation process, do not close the evaluation progress window.

Figure 58 Simulation completed

Evaluate simulation

About this feature

Perform this task to evaluate the simulation of edited device configurations, and then output the check results to help users review connectivity between devices.

View the simulation evaluation result

On the Evaluate Simulation tab, the system displays the baseline check results, custom access relationship check, and network analysis results. The system supports exporting simulation evaluation reports.

· Baseline detection results: The page displays the detection results of all baselines.

Figure 59 Baseline detection results

¡ The detection results column displays the connectivity results before and after simulation. Click to view baseline results and detection results in the Detection Results dialog box that opens.

Figure 60 Detection result

¡ Click the icon in the Actions column. In the Detection Results dialog box that opens, view the details of the access relationship.

Figure 61 Access relationship details

· Custom access relationship detection > Custom access relationships:

¡ Click Add. Add a new access relationship in the dialog box that opens.

Figure 62 Add access relationship

¡ Click Detect to start custom access relationship detection.

Figure 63 Custom access relationship detection > Custom access relationships

· Custom access relationship detection > Detection results:

¡ The tab displays the custom access relationship detection results, including reachable, unreachable, and total counts.

¡ Click the icon to view the detailed access relationships and their detection results on the topology.

Figure 64 Custom access relationship detection > Detection results

· Export simulation evaluation report

To export the simulation evaluation report, click Export Simulation Evaluation Report in the upper right corner of the Evaluate Simulation page. This report displays service change records, baseline detection results, custom access relationship detection results, abnormal connection diagnosis, and abnormal route analysis.

Figure 65 Export simulation evaluation report

Configure basic services for tenant service simulation

NOTE:

· Make sure SeerEngine-DC and DTN have been deployed. For the deployment process, see H3C SeerEngine-DC Installation Guide (Unified Platform) and H3C SeerEngine-DC Simulation Installation Guide.

· In the current software version, system administrators and tenant administrators can configure simulation services.

Configuration workflow

Figure 66 Configuration flowchart

Procedure

Preconfigure tenant service simulation

Adding simulation hosts

1. Log in to the controller.

2. Access the Automation > Data Center Network > Simulation > Build Simulation Network page.

3. Click Preconfigure Simulation Network. The Manage Simulation Hosts page opens.

4. Click Add. In the dialog box that opens, configure the host name, IP address, username, and password.

Figure 67 Adding simulation hosts

5. Click Apply.

NOTE:

· A simulation host can only be managed by one controller.

· The controller supports both root and non-root users to manage simulation hosts. When incorporating simulation hosts as a non-root user, you must add the non-root user privilege before incorporating the hosts as follows: Execute the sudo ./addPermission.sh username command in the SeerEngine_DC_DTN_HOST-version/tool/ directory decompressed from the SeerEngine_DC_DTN_HOST package.

· If you edit the configuration of a simulation host, add the simulation host on the page again.

Uploading simulation images

1. Access the Automation > Data Center Network > Simulation > Build Simulation Network page, click Simulation Network Preconfiguration, and then click the Simulation Image Management tab.

2. Click Upload Image. In the dialog box that opens, select the type of the image to be uploaded and image of the corresponding type, and then click Upload.

Figure 68 Uploading simulation images

Configuring parameters-license server deployment

The license server provides licensing services for simulated devices. The following deployment modes are supported:

(Recommended) Use a license server that has been deployed using the controller (the IP protocol type of the license server must match the IP protocol type of the DTN component MACVLAN network).

Deploy a license server for each simulation host. If there are multiple simulation hosts, upload the License Server installation package to any one of the servers.

NOTE:

· To install the license server separately, see H3C License Server Installation Guide.

· When you deploy the DTN component, the system registers the license with Unified Platform. For more information, access the System > License Management > License Information page. The license named AD-DC Management License for Value-Added Service Security Simulation, 1 Device does not immediately obtain license authorization from the license server after a device connects to the license server. Its authorization status might not be displayed as normal. The system requests and obtains the corresponding license from the server only when you build a simulation network and actually need the license.

Configuring parameters

1. Navigate to the Automation > Data Center Networks > Simulation > Build Simulation Network page. Click Preconfigure. On the page that opens, click the Parameters tab.

2. This page allows you to view and modify basic information, UDP tunnel information, address pool information, and supports configuration of License Server-related parameters.

Figure 69 Configure parameters

3. Click OK.

Adding reserved ports in the configuration file

To avoid the configured UDP ports from being occupied, configure this port range as reserved ports on the simulation host. The specific operation is as follows:

1. Access the backend of the simulation host, use the vi /etc/sysctl.conf command to enter the sysctl.conf configuration file, and add the following configuration.

[root@node1 ~]# vi /etc/sysctl.conf

...

net.ipv4.ip_local_reserved_ports=10000-15000

2. If the UDP port range has been modified on the page, update the reserved port range in the sysctl.conf configuration file to match the currently configured UDP port range on the page, and save the changes.

3. Execute the /sbin/sysctl –p command to make the changes effective.

4. Execute the cat /proc/sys/net/ipv4/ip_local_reserved_ports command to view the reserved ports. If the returned range matches the modified range, the modification is complete.

Build a simulation network

Online building

1. Log in to the controller.

2. Access the Automation>Data Center Network>Simulation>Build Simulation Network page.

3. Click Build Simulation Network to access the build simulation network process page. Select online data as the data source, and then click Next.

Figure 70 Select a data source

4. Select fabrics as needed, and then click Start Building to start building the simulation network. You can select multiple fabrics.

Figure 71 Select fabrics

5. After a simulation network is built, the network is displayed as Built on this page.

Figure 72 Built a simulation network successfully

6. The successfully built simulation network allows you to view simulation device information:

¡ The simulation status is Active.

¡ The device model is displayed correctly on the production network and the simulation network.

¡ The VMs in the simulation network model are created on the host created. If multiple hosts are available, the controller selects a host with optimal resources for creating VMs.

Offline building

To use the offline data to build a simulation network, first back up and restore the environment, and obtain the link information and device configuration files before building a simulation network.

1. Back up the SeerEngine-DC environment

a. Log in to the controller that is operating normally. Navigate to the System > Emergency Management > Backup & Restore page.

b. Click Start Backup. In the dialog box that opens, select SeerEngine-DC. Click Backup to start backup.

Figure 73 Backing up the controller

c. After the backup is completed, click Download in the Actions column for the backup file to download it.

2. Obtain the device configuration file

a. Log in to the controller that is operating normally. Navigate to the Management > Data Center Management > Device Maintenance > Physical Devices page.

b. Select all devices, and click Manual Backup.

Figure 74 Manually backing up all device information

c. Click the icon in the Actions column for a device. The configuration file management page opens. Click Download to download the configuration file of the specified device to your local host.

Figure 75 Configuration file management page

d. Compress all download configuration files into one .zip package. The .zip package name is not limited. The .zip package is the device configuration file.

3. Obtain the link information file through either of the following methods:

Method 1:

a. In the address bar of the browser, enter http://ip_address:port/sdn/ctl/rest/topologydata/all_link_info and then press Enter. Link information of all fabrics in the environment will be displayed. ip_address represents the northbound service VIP of the Unified Platform cluster. port represents the port number.

b. Copy the obtained link information to a .txt file, and save the file. The file name is not limited. The file is the link information file.

Method 2:

c. Log in to the controller.

d. Access the Automation > Data Center Network > Simulation > Build Simulation Network page.

Figure 76 Building a simulation network

e. Click Build Simulation Network to enter the build simulation network process page, selecting offline data as the data source.

Figure 77 Offline data

f. On the link information tab, click Import. In the dialog box that opens, click Download Link Template to download the link template.

Figure 78 Downloading link template

g. Edit the information in the template, and after modifications, upload the link information file.

4. Restore the SeerEngine-DC environment

a. Log in to the environment where you want to build a simulation network based on offline data.

b. Navigate to the System > Emergency Management > Backup & Restore page. Use the backup file to restore the environment.

Figure 79 Restore the environment

5. Build a simulation network

a. Log in to the controller.

b. Access the Automation > Data Center Network > Simulation> Build Simulation Network page.

Figure 80 Building a simulation network

c. Click Build Simulation Network to access the build simulation network process page, with offline data selected as the data source.

Figure 81 Offline data

d. On the Device Info page, click Import. In the dialog box that opens, import and upload the device configuration file.

Figure 82 Importing and uploading the device configuration file

e. On the Down Link Info page, click Import. In the dialog box that opens, import and upload the link information file. Skip this step if the link information has already been imported.

f. Click Next.

g. Select fabrics as needed, and click Start Building to start building the simulation network. You can select multiple fabrics.

h. After a simulation network is built, the network is displayed as Built on this page.

i. The successful simulation network has been established, and you can view the simulated device information.

- The simulation status is Active.

- The device model is displayed correctly on the production network and the simulation network.

The VMs in the simulation network model are created on the host created. If multiple hosts are available, the controller selects a host with optimal resources for creating VMs.

Tenant service simulation

Enabling tenant design mode and simulation baselining

1. On the top navigation bar, click Automation.

2. From the navigation pane, select Data Center Networks > Simulation > Tenant Service Simulation. You are placed on the Enable Design Mode page by default.

3. Enable design mode for the specified tenant. When the design mode is enabled, the tenant icon is displayed as . When the design mode is disabled, the tenant icon is displayed as .

NOTE:

You can enable the design mode and then perform tenant service simulation only when the simulation network is built normally.

Figure 83 Enable the tenant design mode

4. Click Next to access the Simulation Baselining page.

5. On the simulation baseline page, click Execute to start the simulation baseline process.

NOTE:

As a best practice to provide baseline values for network-wide impact analysis results, perform simulation baselining after you enable the design mode for a tenant and deploy configuration.

Figure 84 Simulation baselining

Logical network resource orchestration

1. After you enable the design mode and execute simulation baselining, click Next. You are placed on the Service Changes > Logical Networks page by default.

2. Drag a resource icon in the Resources area to the canvas area. Then, a node of this resource is generated in the canvas area, and the configuration panel for the resource node opens on the right. In the canvas area, you can adjust node locations, bind/unbind resource, and zoom in/out the topology.

Figure 85 Logical networks

Application network resource orchestration

1. After you enable the design mode and execute simulation baselining, click Next. You are placed on the Logical Networks page by default.

2. Click the Application Network tab to enter the application network page, where you can configure the application network service resources.

Figure 86 Application network page

Public network resource orchestration

After you enable the design mode and execute simulation baselining, click Next.

You are placed on the Logical Networks page by default. Click the Public Network tab to enter the service resource management page and configure the service resources.

Figure 87 Public network page

Evaluate simulation

After the resource arrangement is completed, click Next to enter the simulation evaluation page. On this page, you can sequentially perform operations such as simulation environment checks, capacity simulation, connectivity simulation, and overall network impact analysis.

Prepare for evaluation

This feature quantifies the evaluation results of various dimensions of the simulation environment through a simulation report scoring matrix, allowing users to better understand the assessment outcomes in a more intuitive way.

Figure 88 Prepare for evaluation

Simulation network check—Evaluate the health of the simulation networks based on factors such as CPU and memory usage of simulated devices.

Data consistency check—Evaluate the service differences between production and simulation networks.

Service change analysis—Analyze from the perspective of whether the service changes are reasonable.

Network-wide impact analysis—Evaluate the existence of baseline values for network-wide impact analysis.

Simulate capacity

This feature is used to calculate device resource consumption and configuration deployment caused by this service change and present them in multiple views in the form of differences. This feature is used to calculate device resource consumption and configuration deployment caused by this service change and present them in multiple views in the form of differences. After you click the Capacity Simulation button, the system calculates the consumed resources this time based on the NETCONF configuration from the current service change and the baseline NETCONF configuration on the device. Also, the system collects the total and consumed device resources, and then calculates the overall resource usage.

· Resource capacity

The resource capacity evaluation function evaluates the resource consumption resulting from this service change. By analyzing the total capacity, consumed capacity, and capacity to be consumed of physical device resources on the network, this feature determines whether this service change will fall into the device resource blackhole.

· Configuration changes

The configuration changes mainly show the differences in NETCONF and command line before and after the business changes.

IMPORTANT:

Configuration distribution is not allowed when the capacity assessment is incomplete or expired.

Figure 89 Simulate capacity

After capacity simulation is completed, the system displays the resource usage and configuration of modified devices. Resource usage includes total capacity, consumed capacity, capacity consumed in this simulation, and overall resource usage. At the same time, click the Configuration Change Details button in the upper right corner of the block diagram to view configuration changes for NETCONF and CLI.

Simulate connectivity

On this page, you can manually select ports for detection according to service requirements. The connectivity simulation feature simulates TCP, UDP, and ICMP protocol packets to detect connectivity between ports.

The connectivity simulation feature uses the Linux packet sending mechanism. The packets are transmitted through the packet-in action through the OpenFlow channel to the DTN-Sandbox-Controller to perform connectivity simulation between vPorts and trace the packet path.

You can manually select ports for detection according to service requirements. The connectivity simulation feature simulates TCP, UDP, and ICMP protocol packets to detect connectivity between ports. A user vPort is simulated by using a Linux namespace. It uses the port packet sending mechanism and uses the packet-in messages to send packets through the OpenFlow channel for path detection. After simulation is completed, the system displays the inter-port paths and displays the failure reasons upon detection failure.

Figure 90 Connectivity detection page

Follow these steps to perform connectivity detection:

2. On the Evaluate Simulation > Connectivity Simulation > Test page, select the source IP addresses and destination IP addresses to be detected.

Figure 91 Select the source IP addresses and destination IP addresses

3. After selection, click the Test button. The system pairs the source and destination IP addresses and detects their reachability. After the detection completes, the system automatically displays the detection results for each pair.

Figure 92 Connectivity detection results

4. Click the Path icon in the Actions column for a path to view its overlay and underlay path information in the dialog box that opens.

Figure 93 Overlay path information

Figure 94 Underlay path information

Network-wide impact analysis

From the perspective of the overall service, network-wide impact analysis can quickly assess the impact of service changes on the connectivity of networks, and identify the links with state changes. This feature compares the initial state results before this simulation with the network-wide impact analysis results of this simulation, and outputs the comparison results. Then, you can quickly view the link state changes of the entire network.

Similar to the connectivity simulation feature, network-wide impact analysis uses the Linux packet sending mechanism. The packets are transmitted through the packet-in action through the OpenFlow channel to the DTN-Sandbox-Controller to perform connectivity simulation between vPorts and trace the packet path. Unlike connectivity simulation, network-wide impact analysis automatically selects a set of up to 254 detection points (including vPorts and egresses to external networks) for the selected tenant based on the port filter and performs detection. At the same time, network-wide impact analysis compares the network-wide link connectivity after the service change with the baseline network-wide link connectivity results before the service change. Network-wide impact analysis compares the detection result differences before and after the service change to assess the impact of the service change on network-wide connectivity from a business-wide perspective.

In the current software version, network-wide impact analysis supports multi-tenant, multi-port filters (vRouters, vNetworks, and subnets), and multiple protocols (ICMP, TCP, and UDP).

The following section is an example of performing network-wide impact analysis with the port filter set to vNetwork:

1. After you select the tenant and protocol type, click Execute. The system will count all vNetworks under the current tenant, use a hash method to filter vPorts under these vNetworks, and pair them for reachability detection.

Figure 95 Perform network-wide impact analysis

2. After network-wide impact analysis is completed, check the evaluation results area to view IP reachability change statistics and the top 5 IP reachability changes caused by the service change. Click the View Details button on the right to see the network-wide impact analysis details and compare IP reachability results before and after the service change.

Configuration deployment

You can click Deploy Configuration to deploy the service configuration to real devices when the simulation evaluation result is as expected. Additionally, you can view details on the deployment details page.

Figure 96 Viewing deployment details

Register the software

After DTN is installed, all functions can be tried within 180 days. To continue using the software beyond this trial period, you must obtain the license authorization.

Install the license on the license server

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

Obtain the DTN component license

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

1. Log in to Unified Platform. On the top navigation bar, click System. From the navigation pane, select License Management > License Information.

2. Configure the license server parameters on the page. The following table describes each parameter.

Table 19 Parameters

Parameter	Description
IP address	The IP address is configured on the license server and used for communication among nodes in the cluster.
Port number	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.

3. The DTN component automatically obtains licensing information after connecting to the license server.

NOTE:

When you deploy the DTN component, the system registers the license with Unified Platform. For more information, access the System > License Management > License Information page. The license named AD-DC Management License for Value-Added Service Security Simulation, 1 Device does not immediately obtain license authorization from the license server after a device connects to the license server. Its authorization status might not be displayed as normal. The system requests and obtains the corresponding license from the server only when you build a simulation network and actually need the license.

Obtain the simulated device license

After installing the license for the product on the license server, connect to the license server on the license management page of the DTN component to obtain the license.

1. Log in to Unified Platform.

2. Access the Automation > Data Center Network > Simulation > Build Simulation Network page.

3. Configure the license server parameters on the page. The following table describes each parameter.

Table 20 Parameters

Parameter	Description
IP address	The IP address is configured on the license server and used for communication among nodes in the cluster.
Port number	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.

4. The simulated device automatically obtains licensing information after connecting to the license server.

Perform backup & restoration

The DTN component is an independent microservice of the controller. On Unified Platform, backing up or restoring the controller will also back up or restore the DTN component. For more information, see H3C Unified Platform Deployment Guide.

Upgrade and uninstall software

This chapter describes the upgrade and uninstallation procedures of the DTN component. For information about the upgrade and uninstallation procedures of Unified Platform, see H3C Unified Platform Deployment Guide.

Upgrade DTN

Upgrade the DTN component

Restrictions and guidelines

On Matrix, you can upgrade a component with its configuration retained. Upgrading components might cause service interruption. Please perform this operation with caution.

After upgrading the DTN component, please check the simulation software version. If there are updates, please upgrade them accordingly.

Upgrade DC and then DTN. The upgraded version of DTN must be consistent with the version of DC.

If the webpage for building simulation networks cannot display information correctly after a DTN component upgrade, clear the cache in your Web browser and log in again.

When upgrading the DTN component from version E6102 or earlier to E6103 or later, the simulation device host must be reinstalled with the operating system and reconfigured. For the steps to install and configure the simulation device host, see "Deploy the simulation hosts (standalone deployment)." After the upgrade, the original host in the simulation network must be deleted and re-managed.

After upgrading the DTN component from version E6202 or earlier to E6203 or later, please uninstall the simulation device host and reconfigure it. For the steps to uninstall and configure the simulation device host, see "Uninstall a simulation host." After the upgrade, the original host in the simulation network must be deleted and re-managed.

After upgrading the DTN component from version E6302 or earlier to E6302 or later, all simulation networks in the Fabric must be deleted and then rebuilt.

The DTN component does not support direct upgrade from versions earlier than E6501 to E6501 or later. The old version must be uninstalled and the DTN component reinstalled.

Procedure

1. Log in to Matrix.

2. On the top navigation bar, click DEPLOY. From the navigation pane, select Convergence Deployment.

3. Click the icon to the left of the data center scenario to expand the information.

4. Click the icon in the Actions column for the DTN component to access the upgrade page.

5. Click Upload. In the window that opens, select the target installation package.

Figure 97 Upload the target installation package

6. Select the uploaded installation package, and then click Upgrade to upgrade the DTN component.

Figure 98 Upgrade the DTN component

7. If the component upgrade fails, click Roll Back to roll back the components to the versions before the upgrade.

Upgrade the DTN component through a hot patch

Restrictions and guidelines

The Matrix page supports patch upgrades for reserved configurations of controllers. Please proceed with caution, as patch upgrades may cause interruptions in the controller's operations.

Procedure

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

2. Click the icon to the left of the data center scenario to expand the information.

3. Click the icon in the Actions column for the DTN component to access the hot patch management page.

4. Click Upload, and then select the target hot patch installation package.

Figure 99 Upload the hot patch installation package

5. Select the DTN hot patch installation package, and then click Upgrade.

6. If the hot patch upgrade fails, you can roll back the component to the version before the upgrade or terminate the upgrade.

Uninstall DTN

Uninstall the DTN component

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

2. Click the icon to the left of the data center scenario to expand the information.

3. Select the checkbox on the left of the DTN component, and click Uninstall to uninstall the component.

Figure 100 Uninstall the DTN component

Uninstall the DTN hot patch

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

2. Click the icon to the left of the data center scenario to expand the information.

3. Click the icon in the Actions column for the DTN component to access the hot patch management page.

Figure 101 Access the hot patch management page

4. Click Uninstall, select the baseline version to which the component will be rolled back and verify that the baseline installation package exists.

5. Click OK.

Upgrade a simulation host

Upgrade the simulation hosts deployed in standalone mode

1. Obtain the SeerEngine_DC_DTN_HOST installation package, upload it to the server, and then decompress it. The installation package name is SeerEngine_DC_DTN_HOST-version.zip, where version represents the software version number. In this example, the version number is E7101.

[root@host01 root]# unzip SeerEngine_DC_DTN_HOST-E7101.zip

2. Execute the chmod command to assign permissions to the user.

[root@host01 root]# chmod +x -R SeerEngine_DC_DTN_HOST-E7101

3. Access the SeerEngine_DC_DTN_HOST-version/ directory decompressed from the SeerEngine_DC_DTN_HOST installation package, and then execute the ./upgrade.sh command.

[root@host01 SeerEngine_DC_DTN_HOST-E7101]# ./upgrade.sh

check network service ok.

check libvirtd service ok.

check management bridge ok.

check sendip ok.

check vlan interface ok.

Complete!

NOTE:

After upgrading the DTN component from version E6202 or earlier to version E6203 or later, uninstall the simulation host and reconfigure it. After the upgrade, you must delete the original host from the simulation network and add it again.

Uninstall a simulation host

Uninstall the simulation hosts deployed in standalone mode

IMPORTANT:

· To uninstall a simulation host of E6202 or an earlier version, execute the ./uninstall.sh management_nic service_nic command in the specified directory.

Enter the SeerEngine_DC_DTN_HOST-version/ directory, and then execute the ./uninstall.sh command.

[root@host01 SeerEngine_DC_DTN_HOST-E7101]# ./uninstall.sh

Uninstalling ...

Bridge rollback succeeded.

Restarting network,please wait.

Complete!

Network changes

After the controller is deployed, if IP address conflicts occur in the network or if the overall network plan must be changed (such as data center relocation and subnet mask changes), you can edit the network of the component. This chapter introduces the network changes for the DTN component.

IMPORTANT:

· In a remote disaster recovery scenario, before making network changes to the DTN component, you must first remove the disaster recovery system.

· Editing component network settings will cause service interruption. Please be cautious.

Edit network settings

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

2. Click the icon to the left of the data center scenario.

3. Click the icon in the Actions column for the DTN component.

4. Select the target network.

5. Click Next to access the network binding page. Select the target network and subnet.

6. Click Next to verify the configuration.

7. Verify the configuration, and then click OK to deploy the configuration. The page will display the network change progress.

8. If the network change fails, you can roll back the network to its previous state, or exit the network change process.

Tasks after network changes

After network changes, some IP address-related configuration must be edited manually.

Network check

After the DTN network changes, make sure the DTN component is reachable from the simulation hosts.

H3C SeerEngine-DC Simulation Network Deployment Guide-R73xx-6W300

Installation procedure

Hardware requirements (deployment on physical server)

(Recommended.) Converged deployment of DTN component + independent deployment of simulation host

Operating system requirements

Client configuration requirements

Obtain the software packages

Plan the network

Plan IP addresses

Deploy the DTN component (convergence deployment)

Log in to Matrix

Select installation packages

Configure parameters

Configure networks

Bind nodes

Verifying the node information

Deploy the simulation hosts (standalone deployment)

Install the operating system

NingOS operating system

Configure simulation hosts

Deployment across Layer 3 networks

Access the simulation page

Configure parameter settings

Manage simulation images

Manage simulation device hosts

Add a baseline

Configure access relationships

Add a simulation task

Start simulation

Build a simulation model

Configure baselines

Change services

Service change steps in topology view

Service change steps in list view

Configuration deployment

Upgrade the DTN component

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Uninstall DTN

Uninstall the DTN component

Uninstall the DTN hot patch

Upgrade a simulation host

Uninstall a simulation host

Network changes

Tasks after network changes

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