This document provides hardware requirements for AD-NET products, including hardware requirements for single-controller deployment, converged deployment of controller and analyzer, and multi-controller deployment.

· For hardware requirements of Unified Platform, see "Hardware requirements for Unified Platform."

· For hardware requirements of AD-Campus scenarios, see "Hardware requirements for AD-Campus."

· For hardware requirements of AD-DC scenarios, see "Hardware requirements for AD-DC."

· For hardware requirements of AD-WAN scenarios, see "Hardware requirements for AD-WAN."

· For hardware requirements of SeerAnalyzer scenarios including NPA, TRA, and LGA, see "Hardware requirements for SeerAnalyzer (NPA/TRA/LGA)."

· For hardware requirements of the license server, see "Hardware requirements for license server deployment."

· For hardware requirements of converged deployment, see "Hardware requirements for multi-scenario converged deployment."

Applicable component versions

This document is applicable to AD-NET 5.3 and later.

This document is applicable to SeerAnalyzer E62xx and later. For hardware requirements of SeerAnalyzer history versions, see "Hardware requirements for SeerAnalyzer history versions".

Hardware requirements for Unified Platform

Unified Platform supports single-node and cluster deployment modes. In single-node deployment mode, Unified Platform is deployed on a single master node and offers all its functions on this master node. In cluster mode, Unified Platform is deployed on a cluster that contains three master nodes and N (≥ 0) worker nodes, delivering high availability and service continuity. You can add worker nodes to the cluster for service expansion. Unified Platform can be deployed on physical servers or virtual machines (VMs).

Required application installation packages

Table 1 Required application installation packages

Software package name	Feature description	Remarks
common_H3Linux.iso	H3Linux operating system installation package.	Required.
general_PLAT_Middle	Middleware image	Required. Supported in D0712 and later
common_PLAT_glusterfs	Provides local shared storage functionalities.	Required.
general_PLAT_portal	Provides portal, unified authentication, user management, service gateway, and help center functionalities.	Required.
general_PLAT_kernel	Provides the permission, resource identity, license, configuration center, resource group, and logging functionalities.	Required.
general_PLAT_kernel-base	Provides the alarm, access parameter template, monitor template, report, and forwarding via mail or SMS functionalities.	Required in basic network scenarios.
general_PLAT_network	Provides the basic management functionalities (including network resources, network performance, network topology, and iCC)	Required in basic network scenarios.

For the recommended hardware configuration of the required software packages, see "Hardware requirements for Unified Platform (E0711 and later)," and "Hardware requirements for Unified Platform (versions earlier than E0709, including E06xx)." For the hardware configuration of optional software packages, see Table 2.

Table 2 Optional application installation packages

Software package name	Feature description	CPU (cores)		Memory (GB)	Remarks
Software package name	Feature description	x86-64 (Intel64/AMD64)	x86-64 (Hygon) + ARM (Kunpeng 920/Phytium)	Memory (GB)	Remarks
general_PLAT_kernel-region	Provides the hierarchical management function	0.5	1	6	Dependent on general_PLAT_kernel-base
general_PLAT_Dashboard	Provides the dashboard framework	0.5	1	4	Dependent on general_PLAT_kernel-base
general_PLAT_widget	Provides the widgets on the dashboard of the platform	0.5	1	2	Dependent on general_PLAT_Dashboard
general_Websocket	Provides the southbound WebSocket feature.	1	2	8
general_PLAT_suspension	Provides the maintenance tag feature.	0.2	0.4	1
ITOA-Syslog	Provides the syslog feature.	1.5	3	8
CMDB	Provides database configuration and management.	4	8	16	Dependent on general_PLAT_kernel-base
general_PLAT_aggregation	Provides the alarm aggregation feature.	1.5	3	8	Dependent on general_PLAT_kernel-base
general_PLAT_netconf	Provides the NETCONF invalidity check and NETCONF channel features.	3	6	10
general_PLAT_network-ext	Provides the network tool service.	0.5	1	1	Dependent on general_PLAT_network
general_PLAT_oneclickcheck	Provides one-click check.	0.5	1	2	Dependent on general_PLAT_kernel-base
nsm-webdm	Provides NE panels.	2	4	4	Dependent on general_PLAT_network
Analyzer-Collector	Provides data collection through SNMP/NETCONF/GRPC/Syslog/Netstream/Sflow/SNMP-Trap/Flow.	8	16	30	This installation package is required for the analyzer, and you can install the package only on the master nodes. To deploy the analyzer on Unified Platform, first deploy this package. The hardware requirements for deploying this application depend on services running on the analyzer (device quantity, entry quality, tunnel quantity, user quality, and application quality). For more information, see hardware requirements in H3C SeerAnalyzer Deployment Guide.
Analyzer-AIOPS	Provides open prediction and anomaly detection APIs.	4	8	12
general_PLAT_imonitor	Provides the monitoring and alarm feature.	2.5	5	8	Dependent on portal This component can be installed only on the Matrix webpage (port 8443). It cannot be installed on the Unified Platform webpage (port 30000).
general_PLAT_autodeploy	Provides automated device deployment.	2	4	16	Dependent on network This component can be installed only on the Unified Platform webpage (port 30000). It cannot be installed on the Matrix webpage (port 8443).
general_PLAT_snapshot	Provides configuration rollback through a snapshot	1	2	8	portal, kernel
general_PLAT_quickreport	Provides the fast report feature.	2.5	5	8	Dependent on gfs, portal, kernel, and base

Hardware configuration requirements for physical servers and VMs

This section provides the hardware requirements for Unified Platform deployment. For information about a specific scenario, see the hardware requirements of the scenario.

General requirements for Unified Platform deployment

Unified Platform can be deployed on physical servers or VMs. To deploy Unified Platform on a VM, make sure the VM runs on VMware ESXi 6.7.0 or H3C CAS E0706 or later.

Unified Platform supports single-node deployment and cluster deployment.

Table 3 shows the general requirements for Unified Platform deployment.

Table 3 General requirements

Item		Requirements
Drive: · The drives must be configured in RAID 1, 5, or 10. · Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present. · The capacity requirement refers to the capacity after RAID setup.	Drive configuration option 1	· System drive: SSDs configured in RAID, with an IOPS of 5000 or higher. · ETCD drive: SSDs configured in RAID. (Installation path: /var/lib/etcd.)
	Drive configuration option 2	· System drive: 7.2K RPM SATA/SAS HDDs configured in RAID, with an IOPS of 5000 or higher. · ETCD drive: 7.2K RPM or above SATA/SAS HDDs configured in RAID. (Installation path: /var/lib/etcd.)
Network ports		· Non-bonding mode: 1 × 1Gbps network port. · Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.

NOTE:

For Unified Platform E0706 and later versions, the etcd partition can share a physical drive with other partitions. As a best practice, use a separate physical drive for the etcd partition. For information about whether etcd can use a separate physical disk, see the configuration guide for the solution.

Hardware requirements for Unified Platform (E0711 and later)

This section provides the hardware requirements for Unified Platform deployment on physical servers and VMs. The CPU requirements are as follows:

· The number of CPUs is the number of CPU cores when Unified Platform is deployed on physical servers and the number of vCPUs when Unified Platform is deployed on VMs. For example, converged deployment of Unified Platform and the basic network component requires eight CPUs. To deploy them on a physical server, prepare eight CPU cores. To deploy them on a VM, prepare eight vCPUs.

· The CPUs must be exclusively used and cannot be overcommitted. For deployment on physical servers, if the CPUs support double-threading, you can prepare half of the required CPU cores.

Table 4 Single-node deployment of Unified Platform

Components	Minimum node requirements	Maximum resources that can be managed
Unified Platform (OS+ glusterfs +portal+kernel)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 4 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 8 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 8 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 8 cores, 2.1 GHz · Memory: 20 GB. · System drive: 400 GB · ETCD drive: 50 GB	Lite mode: · Network devices: 200 · Network performance collection instances: 10000 · Online users: 5 · Concurrent users: 1 · Notification rate: ≤ 5/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz · Memory: 32 GB. · System drive: 500 GB · ETCD drive: 50 GB
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz · Memory: 56 GB. · System drive: 600 GB · ETCD drive: 50 GB	Common mode (default): · Network devices: 1000 · Network performance collection instances: 50000 · Online users: 50 · Concurrent users: 10 · Notification rate: ≤ 40/sec

Table 5 Cluster deployment

Components	Minimum node requirements	Maximum resources that can be managed
Unified Platform (OS+ glusterfs +portal+kernel)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 6 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 12 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 12 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 12 cores, 2.1 GHz · Memory: 24 GB. · System drive: 500 GB. 300 GB is required for system and platform deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 200 · Network performance collection instances: 10000 · Online users: 5 · Concurrent users: 1 · Notification rate: ≤ 40/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz · Memory: 48 GB. · System disk: 600 GB 400 GB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 10 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 20 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 20 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 20 cores, 2.1 GHz · Memory: 80 GB. · System disk: 800 GB 600 GB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 2000 · Network performance collection instances: 200000 · Online users: 100 · Concurrent users: 20 · Notification rate: ≤ 80/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 12 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 24 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 24 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 24 cores, 2.1 GHz · Memory: 96 GB. · System drive: 1 TB. 800 GB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 5000 · Network performance collection instances: 500000 · Online users: 200 · Concurrent users: 25 · Notification rate: ≤ 80/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 16 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 32 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 32 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 32 cores, 2.1 GHz · Memory: 112 GB. · System drive: 1.2 TB. 1 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 10000 · Network performance collection instances: 1000000 · Online users: 300 · Concurrent users: 30 · Notification rate: ≤ 100/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 18 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 36 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 36 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 36 cores, 2.1 GHz · Memory: 128 GB. · System drive: 1.5 TB. 1.3 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 15000 · Network performance collection instances: 1500000 · Online users: 500 · Concurrent users: 40 · Notification rate: ≤ 100/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 20 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 40 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 40 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 40 cores, 2.1 GHz · Memory: 160 GB. · System drive: 1.8 TB. 1.6 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 20000 · Network performance collection instances: 2000000 · Online users: 600 · Concurrent users: 50 · Notification rate: ≤ 100/sec
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 24 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 48 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 48 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 48 cores, 2.1 GHz · Memory: 192 GB. · System drive: 2.4 TB. 2.2 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Common mode (default): · Network devices: 30000 · Network performance collection instances: 3000000 · Online users: 800 · Concurrent users: 75 · Notification rate: ≤ 100/sec

Components

Minimum node requirements

Maximum resources that can be managed

Unified Platform (OS+ glusterfs +portal+kernel)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 6 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 12 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 12 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 12 cores, 2.1 GHz

· Memory: 24 GB.

· System drive: 500 GB. 300 GB is required for system and platform deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 200

· Network performance collection instances: 10000

· Online users: 5

· Concurrent users: 1

· Notification rate: ≤ 40/sec

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz

· Memory: 48 GB.

· System disk: 600 GB 400 GB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 10 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 20 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 20 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 20 cores, 2.1 GHz

· Memory: 80 GB.

· System disk: 800 GB 600 GB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 2000

· Network performance collection instances: 200000

· Online users: 100

· Concurrent users: 20

· Notification rate: ≤ 80/sec

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 12 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 24 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 24 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 24 cores, 2.1 GHz

· Memory: 96 GB.

· System drive: 1 TB. 800 GB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 5000

· Network performance collection instances: 500000

· Online users: 200

· Concurrent users: 25

· Notification rate: ≤ 80/sec

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

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

¡ x86-64 (Hygon server): Hygon G5 7380 32 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 32 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 32 cores, 2.1 GHz

· Memory: 112 GB.

· System drive: 1.2 TB. 1 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 10000

· Network performance collection instances: 1000000

· Online users: 300

· Concurrent users: 30

· Notification rate: ≤ 100/sec

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 18 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 36 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 36 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 36 cores, 2.1 GHz

· Memory: 128 GB.

· System drive: 1.5 TB. 1.3 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 15000

· Network performance collection instances: 1500000

· Online users: 500

· Concurrent users: 40

· Notification rate: ≤ 100/sec

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 20 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 40 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 40 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 40 cores, 2.1 GHz

· Memory: 160 GB.

· System drive: 1.8 TB. 1.6 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 20000

· Network performance collection instances: 2000000

· Online users: 600

· Concurrent users: 50

· Notification rate: ≤ 100/sec

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 24 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 48 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 48 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 48 cores, 2.1 GHz

· Memory: 192 GB.

· System drive: 2.4 TB. 2.2 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Common mode (default):

· Network devices: 30000

· Network performance collection instances: 3000000

· Online users: 800

· Concurrent users: 75

· Notification rate: ≤ 100/sec

Hardware requirements for Unified Platform (versions earlier than E0709, including E06xx)

Requirements for deployment on physical servers

Unified Platform supports single-node deployment and cluster deployment.

Table 6 Single-node deployment of Unified Platform

Components	Minimum node requirements	Drive and NIC requirements
Unified Platform (OS+ glusterfs +portal+kernel)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 4 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 8 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 8 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 8 cores, 2.1 GHz · Memory: 32 GB. · System drive: 600 GB · ETCD drive: 50 GB	Drives: · The drives must be configured in RAID 1, 5, or 10. · Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present. · Drive configuration option 1: ¡ System drive: SSDs configured in RAID, with an IOPS of 5000 or higher. ¡ ETCD drive: SSDs configured in RAID. (Installation path: /var/lib/etcd.) · Drive configuration option 2: ¡ System drive: 7.2K RPM SATA/SAS HDDs configured in RAID, with an IOPS of 5000 or higher. ¡ ETCD drive: 7.2K RPM SATA/SAS HDDs configured in RAID. (Installation path: /var/lib/etcd.) Network ports: · Non-bonding mode: 1 × 1Gbps network port. · Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz · Memory: 64 GB. · System drive: 1.7 TB · ETCD drive: 50 GB

Components

Minimum node requirements

Drive and NIC requirements

Unified Platform (OS+ glusterfs +portal+kernel)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 4 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 8 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 8 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 8 cores, 2.1 GHz

· Memory: 32 GB.

· System drive: 600 GB

· ETCD drive: 50 GB

Drives:

· The drives must be configured in RAID 1, 5, or 10.

· Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present.

· Drive configuration option 1:

¡ System drive: SSDs configured in RAID, with an IOPS of 5000 or higher.

¡ ETCD drive: SSDs configured in RAID. (Installation path: /var/lib/etcd.)

· Drive configuration option 2:

¡ System drive: 7.2K RPM SATA/SAS HDDs configured in RAID, with an IOPS of 5000 or higher.

¡ ETCD drive: 7.2K RPM SATA/SAS HDDs configured in RAID. (Installation path: /var/lib/etcd.)

Network ports:

· Non-bonding mode: 1 × 1Gbps network port.

· Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz

· Memory: 64 GB.

· System drive: 1.7 TB

· ETCD drive: 50 GB

To add other components, see Table 2 to select an installation package and add hardware resources.

Table 7 Cluster deployment

Components	Minimum node requirements	Drive and NIC requirements
Unified Platform (OS+ glusterfs +portal+kernel)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 4 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 8 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 8 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 8 cores, 2.1 GHz · Memory: 32 GB. · System drive: 500 GB. 300 GB is required for system and platform deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Drives: · The drives must be configured in RAID 1, 5, or 10. · Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present. · Drive configuration option 1: ¡ System drive: SSDs configured in RAID, with an IOPS of 5000 or higher. ¡ ETCD drive: SSDs configured in RAID. (Installation path: /var/lib/etcd.) · Drive configuration option 2: ¡ System drive: 7.2K RPM SATA/SAS HDDs configured in RAID, with an IOPS of 5000 or higher. ¡ ETCD drive: 7.2K RPM SATA/SAS HDDs configured in RAID. (Installation path: /var/lib/etcd.) Network ports: · Non-bonding mode: 1 × 1Gbps network port. · Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· CPU: Select CPUs based on the server type. ¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above ¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz ¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz ¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz · Memory: 64 GB. · System drive: 1.5 TB. 1.3 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB

Components

Minimum node requirements

Drive and NIC requirements

Unified Platform (OS+ glusterfs +portal+kernel)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 4 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 8 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 8 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 8 cores, 2.1 GHz

· Memory: 32 GB.

· System drive: 500 GB. 300 GB is required for system and platform deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Drives:

· The drives must be configured in RAID 1, 5, or 10.

· Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present.

· Drive configuration option 1:

¡ System drive: SSDs configured in RAID, with an IOPS of 5000 or higher.

¡ ETCD drive: SSDs configured in RAID. (Installation path: /var/lib/etcd.)

· Drive configuration option 2:

¡ System drive: 7.2K RPM SATA/SAS HDDs configured in RAID, with an IOPS of 5000 or higher.

¡ ETCD drive: 7.2K RPM SATA/SAS HDDs configured in RAID. (Installation path: /var/lib/etcd.)

Network ports:

· Non-bonding mode: 1 × 1Gbps network port.

· Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· CPU: Select CPUs based on the server type.

¡ x86-64 (Intel64/AMD64): 8 cores, 2.0 GHz or above

¡ x86-64 (Hygon server): Hygon G5 7380 16 cores, 2.2 GHz

¡ ARM (Kunpeng processor): Kunpeng 920 16 cores, 2.6 GHz

¡ ARM (Phytium processor): Phytium S2500 16 cores, 2.1 GHz

· Memory: 64 GB.

· System drive: 1.5 TB. 1.3 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

NOTE:

For Unified Platform versions earlier than E0706 (including E06xx), the etcd partition requires a separate physical drive.

Hardware requirements for deployment on VMs

Table 8 Single-node deployment

Components	Minimum node requirements	Drive and NIC requirements
Unified Platform (OS+ glusterfs +portal+kernel)	· vCPUs: 8 or more · Memory: 32 GB. · System drive: 600 GB · ETCD drive: 50 GB	Drives: · Two virtual drives for the VM, each corresponding to a physical drive on the server. · Install the ETCD drive on a different physical drive than any other drives. · Make sure etcd has exclusive use of the drive where it is installed. · IOPS: 5000 or higher. Network ports: · Non-bonding mode: 1 × 1Gbps network port. · Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· vCPUs: 8 or more · Memory: 64 GB. · System drive: 1.7 TB · ETCD drive: 50 GB

Components

Minimum node requirements

Drive and NIC requirements

Unified Platform (OS+ glusterfs +portal+kernel)

· vCPUs: 8 or more

· Memory: 32 GB.

· System drive: 600 GB

· ETCD drive: 50 GB

Drives:

· Two virtual drives for the VM, each corresponding to a physical drive on the server.

· Install the ETCD drive on a different physical drive than any other drives.

· Make sure etcd has exclusive use of the drive where it is installed.

· IOPS: 5000 or higher.

Network ports:

· Non-bonding mode: 1 × 1Gbps network port.

· Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· vCPUs: 8 or more

· Memory: 64 GB.

· System drive: 1.7 TB

· ETCD drive: 50 GB

To add other components, see Table 2 to select an installation package and add hardware resources.

Table 9 Hardware requirements for cluster deployment

Components	Minimum node requirements	Drive and NIC requirements
Unified Platform (OS+ glusterfs +portal+kernel)	· vCPUs: 8 or more · Memory: 32 GB. · System drive: 500 GB. 300 GB is required for system and platform deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB	Drives: · Two virtual drives for the VM, each corresponding to a physical drive on the server. · Install the ETCD drive on a different physical drive than any other drives. · Make sure etcd has exclusive use of the drive where it is installed. · IOPS: 5000 or higher Network ports: · Non-bonding mode: 1 × 1Gbps network port. · Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.
Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)	· vCPUs: 16 or more · Memory: 64 GB. · System drive: 1.5 TB. 1.3 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster. · ETCD drive: 50 GB

Components

Minimum node requirements

Drive and NIC requirements

Unified Platform (OS+ glusterfs +portal+kernel)

· vCPUs: 8 or more

· Memory: 32 GB.

· System drive: 500 GB. 300 GB is required for system and platform deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

Drives:

· Two virtual drives for the VM, each corresponding to a physical drive on the server.

· Install the ETCD drive on a different physical drive than any other drives.

· Make sure etcd has exclusive use of the drive where it is installed.

· IOPS: 5000 or higher

Network ports:

· Non-bonding mode: 1 × 1Gbps network port.

· Bonding mode (recommended mode: mode 2 or mode 4): 2 × 1 Gbps or above network ports, forming a Linux bonding interface.

Unified Platform (OS+ glusterfs +portal+kernel) + base network management (kernel-base+kernel-network)

· vCPUs: 16 or more

· Memory: 64 GB.

· System drive: 1.5 TB. 1.3 TB is required for system, platform, and component deployment, and 200 GB is reserved for Gluster.

· ETCD drive: 50 GB

IMPORTANT:

· To ensure stability of Unified Platform, do not overcommit hardware resources such as CPU, memory, and drive.

· For Unified Platform versions earlier than E0706 (including E06xx), the etcd partition requires a separate physical drive.

Hardware requirements for AD-Campus

AD-Campus can be deployed in single-node mode or cluster mode, and can be deployed on a physical server or VM.

You can deploy the controller and the analyzer separately or in a converged manner.

If you deploy only SeerAnalyzer or deploy the controller and SeerAnalyzer separately in a cluster, the SeerAnalyzer nodes use load balancing mode. Decrease of SeerAnalyzer nodes will decrease analytics performance.

IMPORTANT:

· For Unified Platform versions earlier than E0706 (including E06xx), the etcd partition requires a separate physical drive.

· For Unified Platform E0706 and later versions, the etcd partition can share a physical drive with other partitions. As a best practice, use a separate physical drive for the etcd partition.

Deployment on physical servers (x86-64: Intel64/AMD64)

Table 10 General requirements

Item		Requirements
Drive: · The drives must be configured in RAID 1, 5, or 10. · Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present. · The capacity requirement refers to the capacity after RAID setup.	System drive	SSDs or SATA/SAS HDDs configured in RAID that provides a minimum total drive size of 2.4 TB. For HDDs, the rotation speed must be 7.2K RPM or higher.
	ETCD drive	SSDs or 7.2K RPM or above SATA/SAS HDDs configured in RAID that provides a minimum total drive size of 50 GB. Installation path: /var/lib/etcd.
	Data drive	SSDs or SATA/SAS HDDs. As a best practice, configure RAID 5 by using three or more data drives.
Network ports		· Non-bonding mode: One NIC that has one 1Gbps network port. If the node also acts as an analyzer, one more network port is required. As a best practice, use a 10 Gbps network port. · Bonding mode (mode 2 and mode 4 are recommended): Two NICs, each NIC having two 1Gbps network ports. If the node also acts as an analyzer, two more network ports are required. As a best practice, use two 10 Gbps network ports to set up a Linux bonding interface. Upon converged deployment of the analyzer, controller, and Unified Platform, configure the controller and Unified Platform to share a network port, and configure the analyzer to use a separate northbound network port. If only one northbound network port is available, configure the controller and the northbound network of the analyzer to share a network port, and configure Unified Platform to use a separate network port. If the analyzer uses a unified northbound and southbound network, configure the analyzer and controller to share a network port.

NOTE:

If the NIC of the server provides 10-GE and GE ports, configure Unified Platform and the analyzer to share the 10-GE port and the controller to use the GE port alone.

In the following tables, the radio of switches to ACs/APs is 1:3.

Standalone deployment of controller

Table 11 Standalone deployment of controller on a single node (Unified Platform + vDHCP + SE + EIA + WSM (Oasis excluded) )

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	1	· CPU: 24 cores, 2.0 GHz · Memory: 128 GB. · System drive: 2.4 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 2000 online users · 400 switches, ACs, and APs in total
Controller node	1	· CPU: 24 cores, 2.0 GHz · Memory: 128 GB. · System drive: 2.4 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 5000 online users · 1000 switches, ACs, and APs in total

Table 12 Standalone deployment of controller in a cluster (Unified Platform + vDHCP + SE + EIA + WSM (Oasis excluded) )

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	3	· CPU: 22 core, 2.0 GHz. · Memory: 128 GB. · System drive: 2.4 TB after RAID setup · ETCD drive: 50 GB (after RAID setup)	· 2000 online users · 400 switches, ACs, and APs in total
Controller node	3	· CPU: 22 core, 2.0 GHz. · Memory: 128 GB. · System drive: 2.4 TB after RAID setup · ETCD drive: 50 GB (after RAID setup)	· 5000 online users · 1000 switches, ACs, and APs in total
Controller node	3	· CPU: 24 cores, 2.0 GHz · Memory: 128 GB. · System drive: 2.4 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 10000 online users · 2000 switches, ACs, and APs in total
Controller node	3	· CPU: 24 cores, 2.0 GHz · Memory: 144 GB. · System drive: 2.7 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 20000 online users · 4000 devices, including switches, ACs, and APs.
Controller node	3	· CPU: 26 cores, 2.0 GHz · Memory: 144 GB. · System drive: 3.0 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 40000 online users · 8000 devices, including switches, ACs, and APs.
Controller node	3	· CPU: 36 cores, 2.0 GHz · Memory: 160 GB. · System drive: 3.2 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 60000 online users · 12000 devices, including switches, ACs, and APs.
Controller node	3	· CPU: 36 cores, 2.0 GHz · Memory: 176 GB. · System drive: 3.4 TB (after RAID setup) · ETCD drive: 50 GB (after RAID setup)	· 100000 online users · 20000 devices, including switches, ACs, and APs.

Standalone deployment of SeerAnalyzer

The hardware requirements for analyzer deployment vary by analyzer version. This document describes only the hardware requirements for SeerAnalyzer E62xx and later. For hardware requirements of SeerAnalyzer history versions, see "Hardware requirements for SeerAnalyzer history versions".

Table 13 Independent deployment of the analyzer in single-node mode (Unified Platform + SA)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Analyzer node	1	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 192 GB. · System drive: 2.4 TB after RAID setup · Data drive: 2 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 2000 online users · 400 switches, ACs, and APs in total
Analyzer node	1	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 192 GB. · System drive: 2.4 TB after RAID setup · Data drive: 2 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 5000 online users · 1000 switches, ACs, and APs in total
Analyzer node	1	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 192 GB. · System drive: 2.4 TB after RAID setup · Data drive: 3 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 10000 online users · 2000 switches, ACs, and APs in total
Analyzer node	1	· CPU: 24 cores (total physical cores), 2.0 GHz · Memory: 224 GB. · System drive: 3 TB after RAID setup · Data drive: 4 TB after RAID setup. 3 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 20000 online users · 4000 switches, ACs, and APs in total
Analyzer node	1	· CPU: 28 cores (total physical cores), 2.0 GHz · Memory: 256 GB · System drive: 3 TB after RAID setup · Data drive: 5 TB after RAID setup. 4 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 40000 online users · 8000 switches, ACs, and APs in total
Analyzer node	1	· CPU: 32 cores (total physical cores), 2.0 GHz · Memory: 288 GB · System drive: 3 TB after RAID setup · Data drive: 7 TB after RAID setup. 5 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 60000 online users · 12000 switches, ACs, and APs in total
Analyzer node	1	· CPU: 40 cores (total physical cores), 2.0 GHz · Memory: 384 GB. · System drive: 3 TB after RAID setup · Data drive: 11 TB after RAID setup. 8 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 100000 online users · 20000 switches, ACs, and APs in total

Table 14 Standalone deployment of SeerAnalyzer in a cluster (Unified Platform + SA)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Analyzer node	3	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 128 GB. · System drive: 2.4 TB after RAID setup · Data drive: 2 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 2000 online users · 400 switches, ACs, and APs in total
Analyzer node	3	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 128 GB. · System drive: 2.4 TB after RAID setup · Data drive: 2 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 5000 online users · 1000 switches, ACs, and APs in total
Analyzer node	3	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 128 GB. · System drive: 2.4 TB after RAID setup · Data drive: 2 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 10000 online users · 2000 switches, ACs, and APs in total
Analyzer node	3	· CPU: 20 cores (total physical cores), 2.0 GHz · Memory: 160 GB. · System drive: 3 TB after RAID setup · Data drive: 3 TB after RAID setup. 2 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 20000 online users · 4000 switches, ACs, and APs in total
Analyzer node	3	· CPU: 24 cores (total physical cores), 2.0 GHz · Memory: 192 GB. · System drive: 3 TB after RAID setup · Data drive: 4 TB after RAID setup. 3 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 40000 online users · 8000 switches, ACs, and APs in total
Analyzer node	3	· CPU: 28 cores (total physical cores), 2.0 GHz · Memory: 224 GB. · System drive: 3 TB after RAID setup · Data drive: 5 TB after RAID setup. 4 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 60000 online users · 12000 switches, ACs, and APs in total
Analyzer node	3	· CPU: 32 cores (total physical cores), 2.0 GHz · Memory: 256 GB · System drive: 3 TB after RAID setup · Data drive: 8 TB after RAID setup. 6 or more drives of the same model are required. · ETCD drive: 50 GB (after RAID setup). Installation path: /var/lib/etcd.	· 100000 online users · 20000 switches, ACs, and APs in total

Converged deployment of the controller and analyzer

Converged deployment of the controller and analyzer supports the following modes:

· Converged deployment of the controller and analyzer in single-node mode. For the hardware requirements, see Table 15.

· Converged deployment of the controller and analyzer in 3+N cluster mode. In this mode, deploy the controller on three master nodes and deploy the analyzer on N (1 or 3) worker nodes. For hardware requirements, see the hardware requirements for standalone controller deployment and standalone analyzer deployment.

NOTE:

For converged deployment of the controller and analyzer in 3+N cluster mode, the Oasis and Analyzer-Collector services required by the analyzer will be deployed on the master nodes. Therefore, in addition to the hardware resources required by the controller, you must also reserve the hardware resources required by the Oasis and Analyzer-Collector services on the master nodes. For the hardware requirements of the Oasis service, see Table 31. For the hardware requirements of the Analyzer-Collector service, see Table 2.

· Converged deployment of the controller and analyzer in a three-node cluster mode. In this mode, deploy the controller and analyzer on three master nodes. For hardware requirements, see Table 16.

This section describes the hardware requirements for converged deployment of SeerAnalyzer E62xx or later and the controller.

Table 15 Converged deployment of the controller and analyzer in single-node mode (Unified Platform + vDHCP + SE + EIA + WSM + SA)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller and analyzer	1	· CPU: 38 cores, 2.0 GHz · Memory: 272 GB. · System drive: 2.4 TB (after RAID setup) · Data drive: 2 TB or above after RAID setup. If HDDs are used, two HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 2000 online users · 400 devices, including switches, ACs, and APs.
Controller and analyzer	1	· CPU: 38 cores, 2.0 GHz · Memory: 304 GB. · System drive: 2.4 TB (after RAID setup) · Data drive: 2 TB or above after RAID setup. If HDDs are used, two HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 5000 online users · 1000 devices, including switches, ACs, and APs.

Table 16 Converged deployment of the controller and analyzer in three-node cluster mode (Unified Platform + vDHCP + SE + EIA + WSM + SA)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller and analyzer	3	· CPU: 36 cores, 2.0 GHz · Memory: 224 GB. · System drive: 3 TB (after RAID setup) · Data drive: 2 TB or above after RAID setup. If HDDs are used, two HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 2000 online users · 400 devices, including switches, ACs, and APs.
Controller and analyzer	3	· CPU: 36 cores, 2.0 GHz · Memory: 224 GB. · System drive: 3 TB (after RAID setup) · Data drive: 2 TB or above after RAID setup. If HDDs are used, two HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 5000 online users · 1000 devices, including switches, ACs, and APs.
Controller and analyzer	3	· CPU: 40 cores, 2.0 GHz · Memory: 240 GB. · System drive: 3.2 TB (after RAID setup) · Data drive: 2 TB or above after RAID setup. If HDDs are used, two HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 10000 online users · 2000 devices, including switches, ACs, and APs.
Controller and analyzer	3	· CPU: 38 cores, 2.0 GHz · Memory: 256 GB. · System drive: 3.8 TB (after RAID setup) · Data drive: 3 TB or above after RAID setup. If HDDs are used, two HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 20000 online users · 4000 devices, including switches, ACs, and APs.
Controller and analyzer	3	· CPU: 44 cores, 2.0 GHz · Memory: 288 GB. · System drive: 4.1 TB (after RAID setup) · Data drive: 4 TB or above after RAID setup. If HDDs are used, three HDDs of the same model are required. · ETCD drive: 50 GB or above after RAID setup.	· 40000 online users · 8000 devices, including switches, ACs, and APs.
Controller and analyzer	3	· CPU: 56 cores, 2.0 GHz · Memory: 336 GB. · System drive: 4.3 TB (after RAID setup) · Data drive: 5 TB or above after RAID setup. If HDDs are used, four HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 60000 online users · 12000 devices, including switches, ACs, and APs.
Controller and analyzer	3	· CPU: 58 cores, 2.0 GHz · Memory: 400 GB. · System drive: 4.5 TB (after RAID setup) · Data drive: 8 TB or above after RAID setup. If HDDs are used, six HDDs of the same type are required. · ETCD drive: 50 GB or above after RAID setup.	· 100000 online users · 20000 devices, including switches, ACs, and APs.

DHCP server deployment

The following deployment modes are available:

· H3C vDHCP Server—vDHCP Server can assign IP addresses to devices during onboarding of the devices and assign IP addresses to users and endpoints that access the network. You can use vDHCP Server to assign IP addresses to users if the number of online endpoints does not exceed 50000. vDHCP Server and Unified Platform are installed on the same server or group of servers.

Table 17 Hardware requirements for vDHCP deployment in single-node or cluster mode

Node configuration			Allocatable IP addresses
Node name	Node quantity	Minimum single-node requirements	Allocatable IP addresses
vDHCP node	1 or 3	· CPU: 1 core, 2.0 GHz. · Memory: 2 GB.	· ≤ 15000
vDHCP node	1 or 3	· CPU: 1 core, 2.0 GHz. · Memory: 3 GB.	· ≤ 50000

· Windows DHCP Server—If you do not use vDHCP Server to assign IP addresses to endpoints and no other DHCP server is deployed, you can use the DHCP server service provided with the Windows operating system to assign IP addresses to endpoints. Make sure the operating system is Windows Server 2012 R2 or a higher version. As a best practice, use Windows Server 2016. If the number of online endpoints is greater than 15000, the Windows DHCP Server must be deployed separately. As a best practice, deploy two Windows DHCP servers for HA.

Table 18 Hardware requirements for Windows DHCP server deployed on a physical server

Allocatable IP addresses	Independent Windows DHCP server
≤ 10000	· CPU: 8 cores, 2.0 GHz · Memory: 16GB · Drive: 2 × 300 GB drives in RAID 1 · RAID controller: 256 MB cache
10000 to 40000	· CPU: 16 cores, 2.0 GHz · Memory: 16GB · Drive: 2 × 300 GB drives in RAID 1 · RAID controller: 256 MB cache
40,000 to 60,000	· CPU: 24 cores, 2.0 GHz · Memory: 32GB · Drive: 2 × 500 GB drives in RAID 1 · RAID controller: 1 GB cache
60,000 to 100,000	· CPU: 24 cores, 2.0 GHz · Memory: 64GB · Drive: 2 × 500 GB drives in RAID 1 · RAID controller: 1 GB cache

IMPORTANT:

As a best practice, configure the fail-permit DHCP server for the AD-Campus solution unless declared clearly by the user that is not required. As a best practice, uses a Windows DHCP server deployed in standalone mode as the fail-permit DHCP server.

· Other third-party DHCP Server (for example, InfoBlox, BlueCat, and WRD)—User supplied. It cannot be connected to the AD-Campus controller, and it does support name-IP binding.

EPS deployment

EPS supports single-node deployment and cluster deployment. The following tables describe hardware requirements only for EPS. The hardware requirements for converged deployment of Unified Platform, controller, and EPS are the sum of the hardware requirements for them.

Table 19 Hardware requirements of EPS single-node deployment

Node configuration			Maximum endpoints that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum endpoints that can be managed
EPS nodes	1	· CPU: 4 core, 2.0 GHz. · Memory: 12 GB. · System drive: 100 GB after RAID setup	≤ 10000
EPS nodes	1	· CPU: 6 core, 2.0 GHz. · Memory: 16 GB. · System drive: 200 GB after RAID setup	≤ 20000

Table 20 Hardware requirements for EPS cluster deployment

Node configuration			Maximum endpoints that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum endpoints that can be managed
EPS nodes	3	· CPU: 4 core, 2.0 GHz. · Memory: 6 GB. · System drive: 100 GB after RAID setup	≤ 10000
EPS nodes	3	· CPU: 4 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB after RAID setup	≤ 20000
EPS nodes	3	· CPU: 6 core, 2.0 GHz. · Memory: 12 GB. · System drive: 300 GB after RAID setup	≤ 50000
EPS nodes	3	· CPU: 8 core, 2.0 GHz. · Memory: 16 GB. · System drive: 500 GB after RAID setup	≤ 100000

SMP deployment

In the AD-Campus solution, unified network security management is supported and SMP can be installed based on Unified Platform. In converged deployment, security logging is not supported. The following tables describe hardware requirements only for SMP. The hardware requirements for converged deployment of Unified Platform, controller, and SMP are the sum of the hardware requirements for them.

In cluster deployment mode, SMP uses only the hardware resources on the master node.

Table 21 Hardware requirements for deploying SMP on physical servers

Security devices	Requirements
1 to 10	· CPU: 4 core, 2.0 GHz. · Memory: 10 GB. · Drive: 100 GB
10 to 50	· CPU: 8 core, 2.0 GHz. · Memory: 16 GB. · Drive: 200 GB
50 to 100	· CPU: 16 core, 2.0 GHz. · Memory: 32 GB. · Drive: 500 GB

EIA deployment

EIA supports single-node deployment and cluster deployment. The following tables describe hardware requirements only for EIA. The hardware requirements for converged deployment of Unified Platform, controller, and EIA are the sum of the hardware requirements for them.

Table 22 Hardware requirements of EIA single-node deployment

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 24 GB. · System drive: 200 GB after RAID setup	2000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 24 GB. · System drive: 200 GB after RAID setup	5000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 28 GB. · System drive: 300 GB after RAID setup	10000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 28 GB. · System drive: 300 GB after RAID setup	20000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 28 GB. · System drive: 300 GB after RAID setup	40000 online users
Controller node	1	· CPU: 8 core, 2.0 GHz. · Memory: 32 GB. · System drive: 500 GB after RAID setup	60000 online users
Controller node	1	· CPU: 8 core, 2.0 GHz. · Memory: 32 GB. · System drive: 500 GB after RAID setup	100000 online users

Table 23 Hardware requirements for EIA cluster deployment

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 16 GB. · System drive: 200 GB after RAID setup	2000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 16 GB. · System drive: 200 GB after RAID setup	5000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 20 GB. · System drive: 300 GB after RAID setup	10000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 20 GB. · System drive: 300 GB after RAID setup	20000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 20 GB. · System drive: 300 GB after RAID setup	40000 online users
Controller node	3	· CPU: 8 core, 2.0 GHz. · Memory: 24 GB. · System drive: 500 GB after RAID setup	60000 online users
Controller node	3	· CPU: 8 core, 2.0 GHz. · Memory: 24 GB. · System drive: 500 GB after RAID setup	100000 online users

IMPORTANT:

GlusterFS requires 50 GB more space.

EAD deployment

EAD supports single-node deployment and cluster deployment. The following tables describe hardware requirements only for EAD. The hardware requirements for converged deployment of Unified Platform, controller, EIA, and EAD are the sum of the hardware requirements for them.

Table 24 Hardware requirements for EAD single-node deployment

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	1	· CPU: 2 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB after RAID setup	2000 online users
Controller node	1	· CPU: 2 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB after RAID setup	5000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 14 GB. · System drive: 200 GB (after RAID setup)	10000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 14 GB. · System drive: 200 GB (after RAID setup)	20000 online users
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 18 GB. · System drive: 200 GB (after RAID setup)	40000 online users

Table 25 Hardware requirements for EAD cluster deployment

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	3	· CPU: 2 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB or above after RAID setup.	2000 online users
Controller node	3	· CPU: 2 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB or above after RAID setup.	5000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 12 GB. · System drive: 200 GB or above after RAID setup.	10000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 12 GB. · System drive: 200 GB or above after RAID setup.	20000 online users
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 16 GB. · System drive: 200 GB or above after RAID setup.	40000 online users
Controller node	3	· CPU: 6 cores, 2.0 GHz · Memory: 24 GB. · System drive: 500 GB or above after RAID setup.	100000 online users

WSM deployment

Table 26 Software package description

Software package name	Feature description	Remarks
WSM	Basic WLAN management, including wireless device monitoring and configuration.	Required.
Oasis	Intelligent WLAN analysis, including AP statistics, endpoint statistics, issue analysis, one-click diagnosis, one-click optimization, wireless security, Doctor AP, issue resolving, gradual optimization, and application analysis.	Optional

WSM supports single-node deployment and cluster deployment. The following tables describe hardware requirements only for WSM. The hardware requirements for converged deployment of Unified Platform, controller, and WSM are the sum of the hardware requirements for them.

Table 27 Hardware requirements for WSM deployment in single-node mode (including only WSM)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB after RAID setup	2000 online APs
Controller node	1	· CPU: 4 core, 2.0 GHz. · Memory: 12 GB. · System drive: 400 GB after RAID setup	5000 online APs

Table 28 Hardware requirements for WSM deployment in cluster mode (including only WSM)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 8 GB. · System drive: 200 GB after RAID setup	2000 online APs
Controller node	3	· CPU: 4 core, 2.0 GHz. · Memory: 12 GB. · System drive: 400 GB after RAID setup	5000 online APs
Controller node	3	· CPU: 6 core, 2.0 GHz. · Memory: 16 GB. · System drive: 600 GB after RAID setup	10000 online APs
Controller node	3	· CPU: 6 core, 2.0 GHz. · Memory: 20 GB. · System drive: 800 GB after RAID setup	20000 online APs

Table 29 Hardware requirements for WSM deployment in single-node mode (including WSM and Oasis)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	1	· CPU: 8 core, 2.0 GHz. · Memory: 24 GB. · System drive: 400 GB after RAID setup	2000 online APs
Controller node	1	· CPU: 8 core, 2.0 GHz. · Memory: 28 GB. · System drive: 600 GB after RAID setup	5000 online APs

Table 30 Hardware requirements for WSM deployment in cluster mode (including WSM and Oasis)

Node configuration			Maximum resources that can be managed
Node name	Node quantity	Minimum single-node requirements	Maximum resources that can be managed
Controller node	3	· CPU: 8 core, 2.0 GHz. · Memory: 24 GB. · System drive: 400 GB after RAID setup	2000 online APs
Controller node	3	· CPU: 8 core, 2.0 GHz. · Memory: 28 GB. · System drive: 600 GB after RAID setup	5000 online APs
Controller node	3	· CPU: 12 core, 2.0 GHz. · Memory: 40 GB. · System drive: 1 TB after RAID setup	10000 online APs
Controller node	3	· CPU: 12 core, 2.0 GHz. · Memory: 52 GB. · System drive: 1.5 TB after RAID setup	20000 online APs

Oasis deployment

The following tables describe hardware requirements only for Oasis. The hardware requirements for converged deployment of Unified Platform, controller, and Oasis are the sum of the hardware requirements for them.

Table 31 Hardware requirements for Oasis deployment (applicable to both single-node and cluster modes)

Node name	Minimum single-node requirements	Maximum resources that can be managed
Controller node	· CPU: 4 core, 2.0 GHz. · Memory: 16 GB. · System drive: 200 GB after RAID setup	5000 online APs
Controller node	· CPU: 6 core, 2.0 GHz. · Memory: 24 GB. · System drive: 400 GB after RAID setup	10000 online APs
Controller node	· CPU: 6 core, 2.0 GHz. · Memory: 32 GB. · System drive: 900 GB after RAID setup	20000 online APs

Deployment on physical servers (x86-64 Hygon servers)

IMPORTANT:

For deployment on domestic servers, purchase domestic commercial operating systems as needed.

Table 32 General requirements

Item		Requirements
Drive: · The drives must be configured in RAID 1, 5, or 10. · Storage controller: 1 GB cache, powerfail safeguard module supported, supercapacitor present. · The capacity requirement refers to the capacity after RAID setup.	System drive	SSDs or SATA/SAS HDDs configured in RAID that provides a minimum total drive size of 2.4 TB. For HDDs, the rotation speed must be 7.2K RPM or higher.
	ETCD drive	SSDs or 7.2K RPM or above SATA/SAS HDDs configured in RAID that provides a minimum total drive size of 50 GB. Installation path: /var/lib/etcd.
	Data drive	SSDs or SATA/SAS HDDs. As a best practice, configure RAID 5 by using three or more data drives.
Network ports:		· Non-bonding mode: One NIC that has one 1Gbps network port. If the node also acts as an analyzer, one more network port is required. As a best practice, use a 10 Gbps network port. · Bonding mode (mode 2 and mode 4 are recommended): Two NICs, each NIC having two 1Gbps network ports. If the node also acts as an analyzer, two more network ports are required. As a best practice, use two 10 Gbps network ports to set up a Linux bonding interface. Upon converged deployment of the analyzer, controller, and Unified Platform, configure the controller and Unified Platform to share a network port, and configure the analyzer to use a separate northbound network port. If only one northbound network port is available, configure the controller and the northbound network of the analyzer to share a network port, and configure Unified Platform to use a separate network port. If the analyzer uses a unified northbound and southbound network, configure the analyzer and controller to share a network port.
CPU		Hygon C86 7265, 2.2 GHz

NOTE:

If the NIC of the server provides 10-GE and GE ports, configure Unified Platform and the analyzer to share the 10-GE port and the controller to use the GE port alone.

In the following tables, the radio of switches to ACs/APs is 1:3.