Gateway Solution Selection
In large- and medium-sized campus networks, the virtualization solution is classified into the centralized gateway solution and distributed gateway solution based on the user gateway location. You can select a gateway solution when creating a fabric on iMaster NCE-Campus. In the centralized gateway solution, a border node functions as the gateway of all users, and all inter-subnet traffic is forwarded by the border node. In the distributed gateway solution, multiple edge nodes function as user gateways, and inter-subnet traffic is forwarded through these edge nodes, as shown in Figure 2-1.
When designing the virtualization solution, first determine the gateway solution to be used. After the gateway solution is determined, you can perform end-to-end design on the entire campus network based on the selected gateway solution. Table 2-1 compares the two gateway solutions, and Table 2-2 provides their recommended networking and application scenarios.
Item |
Centralized Gateway |
Distributed Gateway |
|---|---|---|
User gateway location |
Border node |
Edge node |
O&M deployment |
A border node functions as the gateway of all users, and the native WAC function is typically enabled on the border node to configure wireless services, simplifying O&M deployment. |
Multiple edge nodes function as user gateways, and the native WAC function is typically enabled on these edge nodes. Wireless services need to be configured on all edge nodes, complicating O&M deployment. |
Terminal scale |
≤ 50,000 (calculated based on the number and specifications of centralized gateways). This solution is recommended when the number of terminals does not exceed 50,000. |
≤ 100,000 (calculated based on the number and specifications of distributed gateways). This solution is recommended when the number of terminals exceeds 50,000. |
Gateway Solution |
Border Node Location |
Edge Node Location |
WAC Type and Location |
Wireless Data Forwarding Mode |
Application Scenario |
|---|---|---|---|---|---|
Centralized gateway |
Core |
Access |
Native WAC, located on the core device |
Tunnel forwarding |
New network with no more than 50,000 terminals |
Centralized gateway |
Core |
Aggregation |
Native WAC, located on the core device |
Tunnel forwarding |
Reconstructed network with no more than 50,000 terminals. Non-VXLAN access switches can be reused. |
Centralized gateway |
Core |
Access |
Standalone WAC, which is connected to the core device in off-path mode. |
Tunnel forwarding |
Reconstructed network with no more than 50,000 terminals. Standalone WACs can be reused. |
Centralized gateway |
Core |
Aggregation |
Standalone WAC, which is connected to the core device in off-path mode. |
Tunnel forwarding |
Reconstructed network with no more than 50,000 terminals. Standalone WACs and non-VXLAN access switches can be reused. |
Distributed gateway |
Core |
Aggregation |
Native WAC, located on the aggregation device |
Tunnel forwarding |
New or reconstructed network with more than 50,000 and less than or equal to 100,000 terminals. Access switches do not need to support VXLAN. |