A company is using HPE Aruba Networking Central SD-WAN Orchestrator to establish a hub-spoke VPN between branch gateways (BGWs) at 1164 site and VPNCs at multiple data centers. What is part of the configuration that admins need to complete?

In an HPE Aruba Networking Central SD-WAN deployment with multiple data centers (hubs), a crucial configuration step is to define the connectivity paths and failover order for the branch gateways (spokes). This is accomplished within the configuration group for the Branch Gateways (BGWs). Administrators must create a Data Center (DC) preference list that specifies the primary and secondary VPN Concentrators (VPNCs) to which the BGWs should establish tunnels. This ensures that traffic is routed to the preferred data center and that a redundant path is available in case the primary VPNC becomes unreachable. The SD-WAN Orchestrator then uses this preference list to automatically build the required VPN tunnels.

A. VPN pools are typically used to assign IP addresses to remote access VPN clients (e.g., Aruba VIA), not to control which BGWs connect to specific VPNCs.
B. The SD-WAN Orchestrator automates the creation and management of IKE policies for establishing tunnels. Manual creation of default policies is not a required step for the administrator.
D. Similar to IKE policies, the SD-WAN Orchestrator automatically handles the IPsec policies required for the VPN overlay, abstracting this complexity from the administrator during initial setup.

1. HPE GreenLake Edge-to-Cloud Platform User Guide (Aruba Central 2.5.8): In the section "Configuring an SD-Branch Network using the Guided Setup," the "VPN > DC Preference" step is detailed. It states, "The DC Preference page allows you to configure the data center preference for the branch gateways. You can select the primary and secondary data centers for the branch gateways to connect." This directly supports the action described in option C.

2. Aruba SD-Branch Fundamentals Guide: In the chapter "SD-WAN Orchestrator," the section on "Overlay Orchestration" explains that administrators define the network topology (e.g., hub-and-spoke) and preferences. The orchestrator then automatically builds the necessary tunnels with appropriate security parameters, reinforcing that the administrator's primary role is defining connectivity preferences (Option C) rather than manually creating security policies (Options B and D).