You are deploying a new wireless solution with an HPE Aruba Networking Mobility Master (MM), Mobility Controllers (MCs), and campus APs (CAPs). The solution will include a WLAN that uses Tunnel for…

Question

Options

• AOnly links on the path between APs and the core routing switches
• BOnly links on the path between APs and the MC
• CAll links in the campus LAN to ensure seamless roaming
• DOnly links between MC ports and the core routing switches

• A
  10% (2)
• B
  10% (2)
• C
  29% (6)
• D
  52% (11)

Explanation

In an HPE Aruba Networking AOS-8 architecture with a Mobility Master (MM), Mobility Controllers (MCs), and campus APs (CAPs), the WLAN is configured to use Tunnel forwarding mode and WPA3- Enterprise security. In Tunnel mode, all user traffic from the APs is encapsulated in a GRE tunnel and sent to the MC, which then forwards the traffic to the appropriate VLAN. The WLAN is assigned to VLAN 301, and the core routing switches act as the default router for wireless user traffic. Tunnel Forwarding Mode: In this mode, the AP does not directly place user traffic onto the wired network. Instead, the AP tunnels all user traffic to the MC over a GRE tunnel. The MC then decapsulates the traffic and places it onto the wired network in the specified VLAN (VLAN 301 in this case). This means the VLAN tagging for user traffic occurs at the MC, not at the AP. VLAN 301 Assignment: Since the WLAN is assigned to VLAN 301, the MC will tag user traffic with VLAN 301 when forwarding it to the wired network. The core routing switches, acting as the default router, need to receive this traffic on VLAN 301 to route it appropriately. Therefore, VLAN 301 needs to be carried on the links between the MC ports and the core routing switches, as this is where the MC forwards the user traffic after decapsulating it from the GRE

No community discussion yet for this question.