Login
- Released At: 01-06-2023
- Page Views:
- Downloads:
- Table of Contents
- Related Documents
-
|
|
|
AD-DC 6.3 |
|
Unified Platform and Components Deployment Guide |
|
|
|
|
Document version: 5W100-20230513
Copyright © 2023 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
This document provides generic technical information, some of which might not be applicable to your products.
The information in this document is subject to change without notice.
Hardware resource requirements
About cluster separated deployment
About cluster converged deployment
Deploy the Unified Platform application packages
Deploy SeerEngine-DC, vBGP, DTN, and Super Controller
Deploy SeerAnalyzer, collectors, and Super Analyzer-DC
Appendix A Obtain documentation
Overview
Components
This document describes the deployment procedures for the following AD-DC components:
· Unified Platform—Platform component on which you deploy controllers and analyzers.
· SeerEngine-DC—Controller component that runs SDN applications. It controls resources on the network and is the network management center.
· SeerAnalyzer—Analyzer component that provides intelligent analysis for AD-DC solutions.
· vBGP—Virtual BGP component that provides conversion between host overlay flow tables and network overlay EVPN routes. It is typically used in hybrid overlay scenarios.
· Digital-Twin-Network (DTN)—Simulation component that provides the simulation functionality.
· Collector—Collects and sends traffic to SeerAnalyzer.
· Super Controller—Manages the SDN controller cluster in the multi-data center scenario and provides unified service orchestration and O&M across data centers.
· Super Analyzer-DC—Manages multiple analyzers in the cross-data center scenario. It provides NetStream, sFlow, and full-flow data collection and analysis and can implement cross-data center network traffic analysis.
Deployment workflow
Figure 1 Deployment workflow
Hardware resource requirements
For the server hardware resources required to install the components, see AD-NET Solution Hardware Configuration Guide.
Plan network configuration
The following information uses examples to describe how to plan network configuration for Unified Platform and all its components. You can select components for your deployment scenario as required.
Super Controller uses the northbound service VIP of Unified Platform to communicate with sites. You do not need to plan a separate management IP address for it.
The vBGP component supports both the management network and service network converged scheme and management network and service network separated scheme. This document uses the management network and service network converged scheme for the controller for example and the southbound and northbound integrated network (no southbound network) scheme for the analyzer for example.
This section plans only for the management network configuration. For service network configuration, see the network configuration plan for the specific deployment scenario.
The IP address plan in this section is for illustration only.
Standalone deployment
About standalone deployment
The vBGP component is not supported in the standalone deployment scenario.
In a standalone deployment, you deploy SeerEngine-DC, Super Controller, SeerAnalyzer, and Super Analyzer-DC on separate Unified Platform nodes, and deploy the collector on a server other than the Unified Platform nodes.
Connect all the Unified Platform nodes to the management switch and configure the management switch to provide gateway services.
IP address plan
|
Component |
IP address type |
IP addresses |
Remarks |
|
Unified Platform 1 (on which SeerEngine-DC is deployed) |
Master node IP |
192.168.10.102/24 |
These IP addresses must be on the same network segment. Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Cluster internal VIP |
192.168.10.101/32 |
||
|
Northbound service VIP |
192.168.10.100/32 |
||
|
Unified Platform 2 (on which SeerAnalyzer is deployed) |
Master node IP |
192.168.10.202/24 |
These IP addresses must be on the same network segment. Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Cluster internal VIP |
192.168.10.201/32 |
||
|
Northbound service VIP |
192.168.10.200/32 |
||
|
Unified Platform 3 (on which Super Controller is deployed) |
Master node IP |
192.168.10.212/24 |
Super Controller uses the northbound service VIP of Unified Platform to communicate with sites. You do not need to plan a separate management IP address for it. |
|
Cluster internal VIP |
192.168.10.211/32 |
||
|
Northbound service VIP |
192.168.10.210/32 |
||
|
Unified Platform 4 (on which Super Analyzer-DC is deployed) |
Master node IP |
192.168.10.222/24 |
Super Analyzer-DC uses the northbound service VIP of Unified Platform as its management IP address. You do not need to plan a separate management IP address for it. |
|
Cluster internal VIP |
192.168.10.221/32 |
||
|
Northbound service VIP |
192.168.10.220/32 |
||
|
Collector |
Management IP |
192.168.10.50/24 |
Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Southbound collection IP |
11.1.1.0/24 |
You need to configure two IP addresses. Use one to receive mirrored network device packets. Use the other as the SeerCollector float IP for it to be discovered by devices. |
|
|
SeerEngine-DC |
Management network |
Subnet: 192.168.12.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.12.1, which is placed on the management switch. |
|
SeerAnalyzer |
Management network |
Subnet: 192.168.12.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.12.1, which is placed on the management switch. |
Cluster separated deployment
About cluster separated deployment
In a cluster separated deployment, you deploy SeerEngine-DC, SeerAnalyzer (analyzer), Super Controller, and Super Analyzer-DC in separate Uniform Platform clusters, and deploy the collector on a separate physical server.
This document uses the following cluster separated deployment for example:
· Unified Platform cluster 1—Contains three master nodes and one worker node for SeerEngine-DC deployment. vBGP is deployed on two master nodes, and DTN is deployed on the worker node.
· Unified Platform cluster 2—Contains three master nodes for SeerAnalyzer deployment.
· Unified Platform cluster 3—Contains three master nodes for Super Controller deployment.
· Unified Platform cluster 4—Contains three master nodes for Super Analyzer-DC deployment.
· Separate server—Used for collector deployment.
Connect all these servers to the management switch and configure the management switch to provide gateway services. You must use a network interface on each of the two servers on which vBGP is deployed for configuring a management network for vBGP.
The Unified Platform cluster for SeerEngine-DC can span one subnet or multiple subnets. For high availability, you can deploy the master nodes in 2+1+1 mode. For information about address planning and available deployment modes, see H3C SeerEngine-DC Installation Guide. In this deployment example, the nodes are deployed on the same subnet.
IP address plan
|
Component |
IP address type |
IP addresses |
Remarks |
|
Unified Platform cluster 1 (on which SeerEngine-DC is deployed) |
Master node 1 IP |
192.168.10.102/24 |
In this example, all the IP addresses are on the same subnet. Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Master node 2 IP |
192.168.10.103/24 |
||
|
Master node 3 IP |
192.168.10.104/24 |
||
|
Worker node 1 IP (DTN) |
192.168.10.105/24 |
||
|
Cluster internal VIP |
192.168.10.101/32 |
||
|
Northbound service VIP |
192.168.10.100/32 |
||
|
Unified Platform cluster 2 (on which SeerAnalyzer is deployed) |
Master node 4 IP (SeerAnalyzer) |
192.168.10.202/24 |
These IP addresses must be on the same network segment. Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Master node 5 IP (SeerAnalyzer) |
192.168.10.203/24 |
||
|
Master node 6 IP (SeerAnalyzer) |
192.168.10.204/24 |
||
|
Cluster internal VIP |
192.168.10.201/32 |
||
|
Northbound service VIP |
192.168.10.200/32 |
||
|
Unified Platform cluster 3 (on which Super Controller is deployed) |
Master node 7 IP (Super Controller) |
192.168.10.212/24 |
These IP addresses must be on the same network segment. Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Master node 8 IP (Super Controller) |
192.168.10.213/24 |
||
|
Master node 9 IP (Super Controller) |
192.168.10.214/24 |
||
|
Cluster internal VIP |
192.168.10.211/32 |
||
|
Northbound service virtual IP |
192.168.10.210/32 |
||
|
Unified Platform cluster 4 (on which Super Analyzer-DC is deployed) |
Master node 10 IP (Super Analyzer-DC) |
192.168.10.222/24 |
Super Analyzer-DC uses the northbound service VIP of Unified Platform as its management IP address. You do not need to plan a separate management IP address for it. |
|
Master node 11 IP (Super Analyzer-DC) |
192.168.10.223/24 |
||
|
Master node 12 IP (Super Analyzer-DC) |
192.168.10.224/24 |
||
|
Cluster internal VIP |
192.168.10.221/32 |
||
|
Northbound service virtual IP |
192.168.10.220/32 |
||
|
Collector |
Management IP |
192.168.10.50/24 |
Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Southbound collection IP |
11.1.1.0/24 |
You need to configure two IP addresses. Use one to receive mirrored network device packets. Use the other as the SeerCollector float IP for it to be discovered by devices. |
|
|
SeerEngine-DC |
Management network |
Subnet: 192.168.12.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.12.1, which is placed on the management switch. |
|
vBGP |
Management network and service network converged |
Subnet: 192.168.13.0/24 |
Configure OVSDPDK networks. Specify gateway 192.168.13.1, which is placed on the management switch. |
|
DTN |
Management network |
Subnet: 192.168.15.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.12.1, which is placed on the management switch. |
|
DTN host node |
Simulation management network |
Network address pool: 192.168.12.134/24 to 192.168.12.144/24 |
N/A |
|
Simulation device service network |
Network address pool: 192.168.11.134/24 to 192.168.11.144/24 |
N/A |
|
|
Node management network |
Network address pool: 192.168.10.110 to 192.168.10.120 |
N/A |
|
|
SeerAnalyzer |
Management network |
Subnet: 192.168.12.0/24 Network address pool: 192.168.12.141 to 192.168.12.172 |
Configure a MACVLAN-type management network. Specify gateway 192.168.10.1, which is placed on the management switch. |
Cluster converged deployment
About cluster converged deployment
In a cluster converged deployment, you deploy SeerEngine-DC, SeerAnalyzer, Super Controller, and Super Analyzer-DC on one Unified Platform cluster.
This document uses the following cluster converged deployment for example:
· Deploy a Unified Platform cluster that has three master nodes and four worker nodes.
· Deploy SeerEngine-DC and Super Controller on the three master nodes.
· Deploy SeerAnalyzer and Super Analyzer-DC on three of the worker nodes.
· Deploy vBGP on two of the master nodes.
· Deploy DTN on one of the worker nodes.
· Deploy collectors on servers outside of the cluster. In this example, one collector is deployed.
Connect all these servers to the management switch and configure the management switch to provide gateway services. You must use a network interface on each of the two servers on which vBGP is deployed for configuring a management network for vBGP.
IP address plan
|
Component |
IP address type |
IP addresses |
Remarks |
|
Unified Platform |
Master node 1 IP |
192.168.10.102/24 |
These IP addresses must be on the same network segment. Specify gateway 192.168.10.1 for the component, which is placed on the management switch. Super Controller uses the northbound service VIP of Unified Platform to communicate with sites. You do not need to plan a separate management IP address for it. |
|
Master node 2 IP |
192.168.10.103/24 |
||
|
Master node 3 IP |
192.168.10.104/24 |
||
|
Worker node 7 IP (DTN) |
192.168.10.105/24 |
||
|
Worker node 4 IP (SeerAnalyzer) |
192.168.10.202/24 |
These IP addresses must be on the same network segment. Specify gateway 192.168.10.1, which is placed on the management switch. |
|
|
Worker node 5 IP (SeerAnalyzer) |
192.168.10.203/24 |
||
|
Worker node 6 IP (SeerAnalyzer) |
192.168.10.204/24 |
||
|
Cluster internal VIP |
192.168.10.101/32 |
||
|
Northbound service VIP |
192.168.10.100/32 |
||
|
Collector |
Management IP |
192.168.10.50/24 |
Specify gateway 192.168.10.1, which is placed on the management switch. |
|
Southbound collection IP |
11.1.1.0/24 |
You need to configure two IP addresses. Use one to receive mirrored network device packets. Use the other as the SeerCollector float IP for it to be discovered by devices. |
|
|
SeerEngine-DC |
Management network |
Subnet: 192.168.12.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.12.1 for the component, which is placed on the management switch. |
|
vBGP |
Management network |
Subnet: 192.168.13.0/24 |
Configure an OVSDPDK-type management network. Specify gateway 192.168.13.1, which is placed on the management switch. |
|
DTN |
Management network |
Subnet: 192.168.15.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.15.1, which is placed on the management switch. |
|
DTN host node |
Simulation management network |
Network address pool: 192.168.12.134/24 to 192.168.12.144/24 |
N/A |
|
Simulation device service network |
Network address pool: 192.168.11.134/24 to 192.168.11.144/24 |
N/A |
|
|
Node management network |
Network address pool: 192.168.10.110 to 192.168.10.120 |
N/A |
|
|
SeerAnalyzer |
Management network |
Subnet: 192.168.12.0/24 |
Configure a MACVLAN-type management network. Specify gateway 192.168.10.1, which is placed on the management switch. |
Deploy the components
Deploy Unified Platform
For the Unified Platform deployment procedure, see H3C Unified Platform Deployment Guide. For information about how to obtain this document, see "Appendix A Obtain documentation."
To run the controller on Unified Platform, partition the system drive and deploy all required application installation packages required by the controller.
Partition the drive
Partition the drive on the node where a controller resides
Use the following table to partition the drive. Do not use automatic partitioning for the drive.
Table 1 Drive partition settings (2400 GB)
|
RAID configuration |
Partition name |
Mounting point |
Minimum capacity |
Remarks |
|
RAID 10, with a total drive size ≥ 2400 GB |
/dev/sda1 |
/boot/efi |
200 MiB |
EFI system partition, required only in UEFI mode. |
|
/dev/sda2 |
/boot |
1024 MiB |
N/A |
|
|
/dev/sda3 |
/ |
900 GiB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda4 |
/var/lib/docker |
460 GiB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda6 |
swap |
1024 MiB |
Swap partition. |
|
|
/dev/sda7 |
/var/lib/ssdata |
520 GiB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda8 |
N/A |
300 GiB |
Reserved for GlusterFS. You do not need to configure this partition during operating system installation. |
|
|
RAID 1, with a total drive size ≥ 50 GB |
/dev/sdb |
/var/lib/etcd |
50 GiB |
· For a controller in a version earlier than E6203 deployed on Unified Platform in a version earlier than E0706 (including E06xx), make sure the etcd partition has exclusive use of a physical drive. · For a controller in E6203 or later deployed on Unified Platform in E0706 or later, the etcd partition can share a physical drive with other partitions. As a best practice for optimal performance, use a separate drive for the etcd partition. |
Table 2 Drive partition settings (1920 GB)
|
RAID configuration |
Partition name |
Mounting point |
Minimum capacity |
Remarks |
|
RAID 10, with a total drive size ≥ 1920 GB |
/dev/sda1 |
/boot/efi |
200 MiB |
EFI system partition. This partition is required only in UEFI mode. |
|
/dev/sda2 |
/boot |
1024MiB |
N/A |
|
|
/dev/sda3 |
/ |
650 GiB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda4 |
/var/lib/docker |
410 GiB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda6 |
swap |
1024 MiB |
Swap partition |
|
|
/dev/sda7 |
/var/lib/ssdata |
450 GiB |
Supports capacity expansion when the drive size is sufficient |
|
|
/dev/sda8 |
N/A |
220 GiB |
Reserved for GlusterFS. You do not need to configure this partition during operating system installation. |
|
|
RAID 1, with a total drive size ≥ 50 GB |
/dev/sdb |
/var/lib/etcd |
50 GiB |
· For a controller in a version earlier than E6203 deployed on Unified Platform in a version earlier than E0706 (including E06xx), make sure the etcd partition has exclusive use of a physical drive. · For a controller in E6203 or later deployed on Unified Platform in E0706 or later, the etcd partition can share a physical drive with other partitions. As a best practice for optimal performance, use a separate drive for the etcd partition. |
Partition the drives on the node where an analyzer resides
· System drive
Table 3 System drive partition settings
|
RAID configuration |
Partition name |
Mounting point |
Minimum capacity |
Remarks |
|
2*1.92 TB, RAID 1 |
/dev/sda1 |
/boot/efi |
200 MB |
EFI system partition. This partition is required only in UEFI mode. |
|
/dev/sda2 |
/boot |
1024 MB |
N/A |
|
|
/dev/sda3 |
/ |
400 GB |
Supports capacity expansion when the drive size is sufficient. As a best practice, do not save service data in the root directory. |
|
|
/dev/sda4 |
/var/lib/docker |
400 GB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda6 |
swap |
4 GB |
Swap partition. |
|
|
/dev/sda7 |
/var/lib/ssdata |
450 GB |
Supports capacity expansion when the drive size is sufficient. |
|
|
/dev/sda8 |
N/A |
500 GB |
Reserved for GlusterFS. You do not need to configure this partition during operating system installation. |
|
|
2*50 GB, RAID 1 |
/dev/sdb |
/var/lib/etcd |
50 GB |
Make sure etcd has exclusive use of a physical disk. |
· Data drives
Data drives are mainly used to store SeerAnalyzer's service data and Kafka data. The required quantity and capacity of data drives depend on the network scale and amount of service data.
Table 4 Data drive partition configuration (option 1)
|
RAID configuration |
Partition name |
Mounting point |
Minimum capacity |
File system type |
|
3*4 TB, RAID 5 |
/dev/sdc1 |
/sa_data |
400 GB |
ext4 |
|
/dev/sdc2 |
/sa_data/mpp_data |
4800 GB |
ext4 |
|
|
/dev/sdc3 |
/sa_data/kafka_data |
2400 GB |
ext4 |
Table 5 Data drive partition configuration (option 2)
|
RAID configuration |
Partition name |
Mounting point |
Minimum capacity |
File system type |
|
5*4 TB, RAID 5 |
/dev/sdc1 |
/sa_data |
400 GB |
ext4 |
|
/dev/sdc2 |
/sa_data/mpp_data |
9600 GB |
ext4 |
|
|
/dev/sdc3 |
/sa_data/kafka_data |
4800 GB |
ext4 |
Table 6 Data drive partition configuration (option 3)
|
RAID configuration |
Partition name |
Mounting point |
Minimum capacity |
File system type |
|
7*4 TB, RAID 5 |
/dev/sdc1 |
/sa_data |
400 GB |
ext4 |
|
/dev/sdc2 |
/sa_data/mpp_data |
14400 GB |
ext4 |
|
|
/dev/sdc3 |
/sa_data/kafka_data |
7200 GB |
ext4 |
Deploy the Unified Platform application packages
Unified Platform can be installed on x86 or ARM servers. Select the installation packages specific to the server type as described in Table 8 and upload the selected packages. For the installation procedures of the packages, see H3C Unified Platform Deployment Guide.
The common_PLAT_GlusterFS_2.0, general_PLAT_portal_2.0, general_PLAT_kernel_2.0, and general_PLAT_oneclickcheck_2.0 installation packages are required and must be deployed during the Unified Platform deployment process. For the deployment procedure, see "Deploying the applications" in H3C Unified Platform Deployment Guide.
The general_PLAT_kernel-base_2.0, general_PLAT_Dashboard_2.0, and general_PLAT_widget_2.0 installation packages are required. They will be installed automatically during the controller deployment process. You only need to upload the packages.
To use optional applications such as general_PLAT_network_2.0, webdm, Syslog, and general_PLAT_netconf_2.0, deploy them on Matrix manually. You can deploy them before or after SeerEngine-DC components are deployed. To avoid deployment failure, make sure the required and optional packages use the same version. For the deployment procedure, see "Deploying the applications" in H3C Unified Platform Deployment Guide.
Table 7 Installation packages required by the controller
|
Installation package |
Description |
|
· x86: common_PLAT_GlusterFS_2.0_version_x86.zip · ARM: common_PLAT_GlusterFS_2.0_version_arm.zip |
Provides local shared storage functionalities. |
|
· x86: general_PLAT_portal_2.0_version_x86.zip · ARM: general_PLAT_portal_2.0_version_arm.zip |
Provides portal, unified authentication, user management, service gateway, and help center functionalities. |
|
· x86: general_PLAT_kernel_2.0_version_x86.zip · ARM: general_PLAT_kernel_2.0_version_arm.zip |
Provides access control, resource identification, license, configuration center, resource group, and log functionalities. |
|
· x86: general_PLAT_kernel-base_2.0_version_x86.zip · ARM: general_PLAT_kernel-base_2.0_version_arm.zip |
Provides alarm, access parameter template, monitoring template, report, email, and SMS forwarding functionalities. |
|
· x86: general_PLAT_network_2.0_version_x86.zip · ARM: general_PLAT_network_2.0_version_arm.zip |
(Optional.) Provides basic management of network resources, network performance, network topology, and iCC. Install this application if you are to check match of the software versions with the solution or implement network element monitoring and maintenance. |
|
· x86: general_PLAT_Dashboard_2.0_version_x86.zip · ARM: general_PLAT_Dashboard_2.0_version_arm.zip |
Provides the dashboard framework. |
|
· x86: general_PLAT_widget_2.0_version_x86.zip · ARM: general_PLAT_widget_2.0_version_arm.zip |
Provides dashboard widget management. |
|
· x86: general_PLAT_oneclickcheck_2.0_version_x86.zip · ARM: general_PLAT_oneclickcheck_2.0_version_arm.zip |
Provides one-click check. |
|
· x86: general_PLAT_kernel-region_2.0_version_x86.zip · ARM: general_PLAT_kernel-region_2.0_version_arm.zip |
(Optional.) Provides hierarchical management. To use hierarchical management, you need to install the general_ PLAT_ network_ 2.0 application package and use it in tandem with Super Controller for Super Controller to manage DC networks. |
|
· x86: general_PLAT_network_2.0_version_x86.zip · ARM: general_PLAT_network_2.0_version_arm.zip |
(Optional.) Provides basic management of network resources, network performance, network topology, and iCC. Install this application if you need to use the software and solution compatibility check. |
|
· x86: webdm_version_x86.zip · ARM: webdm_version_arm.zip |
(Optional.) Provides the device faceplate feature. To use this feature, you need to install the general_PLAT_network_2.0 application package. |
|
· x86: Syslog-version.zip · ARM: Syslog-version_arm.zip |
(Optional.) Provides Syslog management (log viewing, log-to-alarm escalation rules, and log parsing). Install this application package if you are to use syslog management. |
|
· x86: general_PLAT_netconf_2.0_version_x86.zip · ARM: general_PLAT_netconf_2.0_version_arm.zip |
(Optional.) Provides NETCONF and NETCONF configuration validity check features. Install this application package if you are to use NETCONF service. |
Application packages required for the analyzer nodes
Multiple component packages are available for SeerAnalyzer. Select the component packages as needed.
Table 8 Installation packages required by analyzer nodes
|
Component |
Installation package |
Description |
|
Unified Platform |
common_Linux-<version>.iso |
Installation package of the H3C proprietary Linux operating system. |
|
common_PLAT_GlusterFS_2.0_<version>.zip |
Provides local shared storage functionalities. |
|
|
general_PLAT_portal_2.0_<version>.zip |
Provides portal, unified authentication, user management, service gateway, and help center functionalities. |
|
|
general_PLAT_kernel_2.0_<version>.zip |
Provides access control, resource identification, license, configuration center, resource group, and log functionalities. |
|
|
general_PLAT_kernel-base_2.0_<version>.zip |
Provides alarm, access parameter template, monitoring template, report, email, and SMS forwarding functionalities. |
|
|
general_PLAT_websocket_2.0_<version>.zip |
(Optional.) Provide WebSocket service. This component is required only when the analyzer is deployed on the cloud. |
|
|
general_PLAT_network_2.0_<version>.zip |
(Optional.) Provides basic management of network resources, network performance, network topology, and iCC. Install this application if third-party devices are incorporated on the analyzer. |
|
|
ITOA-Syslog-<version>.zip |
(Optional.) Syslog application. If the northbound service VIP is used for log collection, the analyzer uses the syslog application on Unified Platform. You must install the syslog application on Unified Platform prior to SeerAnalyzer. If the southbound service VIP is used for log collection, the analyzer does not require this application. In the scenario where Analyzer-LGA is deployed on a separate server, you must install the syslog application. |
|
|
general_PLAT_Dashboard_<version>.zip |
Dashboard framework. |
|
|
general_PLAT_widget_2.0_<version>.zip |
Platform dashboard widget. |
|
|
Analyzer-Collector_<version>.zip |
Install this package when deploying the analyzer. |
|
|
general_PLAT_kernel-region_2.0_<version>.zip |
(Optional.) To use IOM proxy in the Analyzer-LGA scenario, install this application. |
|
|
IOM |
COLLECTPLAT_<version>.zip |
(Optional.) Contains the cmc/etcd service and provides features including collection platform configuration management center, alarm computing service, data distribution service, ETCD, task distribution service. To use IOM proxy in the Analyzer-LGA deployment scenario, install this application. |
|
AGENT_<version>.zip |
(Optional.) Provides agent management. To use IOM proxy in the Analyzer-LGA deployment scenario, install this application. |
|
|
AGENT_RECEIVER_<version>.zip |
(Optional.) Provides agent data receipt. To use IOM proxy in the Analyzer-LGA deployment scenario, install this application. |
|
|
AGENT_UPDATER_<version>.zip |
(Optional.) Provides automatic agent update. To use IOM proxy in the Analyzer-LGP deployment scenario, install this application. |
|
|
SeerAnalyzer |
Analyzer-Platform-<version>.zip |
Platform component package. |
|
Analyzer-Telemetry-<version>.zip |
Telemetry component package. |
|
|
Analyzer-NPA-<version>.zip |
Network performance analysis component package. |
|
|
Analyzer-AI-<version>.zip |
AI-driven forecast component package. |
|
|
Analyzer-Diagnosis-<version>.zip |
Diagnosis and analysis component package. |
|
|
Analyzer-SLA-<version>.zip |
Service quality analysis component package. |
|
|
Analyzer-TCP-<version>.zip |
TCP stream analysis component package. |
|
|
Analyzer-WAN-<version>.zip |
WAN application analysis component package. |
|
|
Analyzer-User-<version>.zip |
User analysis component package. |
|
|
Analyzer-AV-<version>.zip |
Audio and video analysis component package. |
|
|
Analyzer-LGA-<version>.zip |
Log analysis component package. |
|
|
Analyzer-TRA-<version>.zip |
Trace analytics component package. |
|
|
H3Linux |
common_H3Linux-<version>.iso |
SeerCollector operating system image file. |
|
NPA traffic collector |
H3CData-<version>.zip |
Collects and sends traffic data to NPA (required in the NPA sceanario). |
Deploy SeerEngine-DC, vBGP, DTN, and Super Controller
Before deploying SeerEngine-DC, make sure the general_PLAT_kernel-base_2.0, general_PLAT_Dashboard_2.0, and general_PLAT_widget_2.0 installation packages have been uploaded. These application packages will be automatically deployed during the SeerEngine-DC deployment process.
For information about the SeerEngine-DC, vBGP, and DTN deployment procedures and required application installation packages, see H3C SeerEngine-DC Controller Installation Guide (Unified Platform). For information about how to obtain the document, see "Appendix A Obtain documentation".
For information about the Super Controller deployment procedure and required application installation packages, see H3C Super Controller Installation Guide (Unified Platform). For information about how to obtain the document, see "Appendix A Obtain documentation".
As a best practice, use the non-RDRS scheme for this solution.
Deploy SeerAnalyzer, collectors, and Super Analyzer-DC
For information about the SeerAnalyzer deployment procedure and required application installation packages, see H3C SeerAnalyzer Deployment Guide. For information about how to obtain the document, see "Appendix A Obtain documentation."
Follow these restrictions and guidelines when you deploy SeerAnalyzer and collectors:
1. To plan the network configuration, see network planning for single-stack southbound network in H3C SeerAnalyzer Deployment Guide.
2. After switching devices are deployed, use an interface on each collector to connect to a leaf device and change the NIC type to DPDK for traffic collection.
For information about the Super Analyzer-DC deployment procedure and required application packages, see H3C Super Analyzer-DC Deployment Guide. For information about how to obtain the document, see "Appendix A Obtain documentation".
Operations monitoring
For information about operations monitoring for this solution, see AD-DC 6.3 Operations Monitoring Configuration Guide.
Appendix A Obtain documentation
To obtain documentation for installing Unified Platform and its components:
1. Access the website at https://www.h3c.com/en/Support/Resource_Center/Technical_Documents/.
2. Select the product category and model and then obtain the document.
Use the following table to obtain the desired documents:
|
Product name |
Manual name |
Directory |
|
Unified Platform |
H3C Unified Platform Deployment Guide-E0708 |
SDN/SeerEngine-DC/Install & Upgrade |
|
SeerEngine-DC |
H3C SeerEngine-DC Installation Guide (Unified Platform )-E63xx |
SDN/SeerEngine-DC/Install & Upgrade |
|
SeerAnalyzer |
H3C SeerAnalyzer Deployment Guide-E63xx |
SDN/SeerEngine-DC/Install & Upgrade |
|
Super Controller |
H3C Super Controller Installation Guide (Unified Platform)-E31xx-5W100 |
SDN/SeerEngine-DC/Install & Upgrade |
|
Super Analyzer-DC |
H3C Super Analyzer-DC Deployment Guide-E63xx |
SDN/Super Analyzer-DC/Install & Upgrade |
