This article is based on a Proof of Concept (PoC) for H3C ADCampus, so every test item is designed backwards from the customer’s real operational needs rather than from a feature checklist.
For large service providers, an application-driven campus network solution is typically evaluated along three dimensions.
First, it must be radically simple to deploy, configure, and operate—because they often manage thousands of devices, and in wireless scenarios the number of APs can explode quickly.
Second, the platform must provide deep and intuitive visibility: analytics should be detailed down to actionable signals, presented in a way that is easy to understand, and ideally paired with one-click optimization or automation so that day-to-day work is minimized and engineers focus on high-level governance instead of repetitive tuning.
Third, access control must be scenario-aware and granular: not only “which authentication type,” but policies that can adapt to context (scene), device, user identity, time windows, and more—while also supporting tenant-oriented management, resource isolation, and clean separation of responsibilities across domains.
Based on the PoC design, the test environment was built with a realistic enterprise campus topology. ADCampus was hosted on a dedicated server at 192.168.1.2/24 (HDM), accessible via 192.168.60.25:30000, providing the central control, analytics, ZTP provisioning, and DHCP services. The platform acts simultaneously as the ZTP server (network segment 120.1.0.0) and DHCP server for multiple address pools: VLAN4094 (130.1.0.10–50), VLAN4093 (130.3.0.10–50), and End Devices (33.1.1.10–50). The EIA authentication service is reachable at 192.168.60.25, while SeerEngine-Campus runs at 50.1.1.2 and SeerEngine-Analyzer at 192.168.60.35.
The aggregation layer is handled by Switch S5130-10P, which connects upstream to the Internet gateway router (G 1/0/1: 192.168.137.10/24, Ge 0/7: 192.168.137.254), to ADCampus (G 1/0/5: 192.168.60.1/24 — Trunk: VLAN 1 20 50 60, PVID VLAN 60), and provides a management uplink (G 1/0/3: 192.168.1.254/24). An end-device laptop is connected on G 1/0/4 (192.168.60.1/24, VLAN 60) with IP 192.168.60.100/24.
The core PoE layer is handled by Switch S6520 PoE++, connected to S5130-10P via G 1/0/6 (VLAN 1 4094). It aggregates all downstream components: two S5130-28P access switches (via Ten1/0/4 and Ten1/0/14, carrying VLAN 1 and 4094; one with DHCP on g 1/0/7 VLAN 1, another on g 1/0/21), and the wireless controllers (via Ten1/0/13 and Ten1/0/23 for WA7539 on VLAN 4093, and Ten1/0/12 and Ten1/0/24 for WA7320i on VLAN 4093). The two ACs form a Cloud-Cluster:
130.3.0.1/24) and VLAN 4094 (130.1.0.3/24); Ge1/0/7 management 192.168.10.0/24; connected to S6520 via Ten1/0/2 (VLAN 4094: 130.1.0.2/24) on VLAN 4093 4094The Internet gateway router provides external connectivity with Ge 0/1 as DHCP-allocated WAN and Ge 0/7 at 192.168.137.254. The physical appearance of the devices and the logical test topology used in this PoC are shown below.
Two APs, Switch and two ACs
bare metal server hosted ADcampus
Test whole Topology