Link Search Menu Expand Document
calendar_month 07-Mar-24

Underlay Orchestration

This section describes how to deploy an OSPF, campus underlay network using the Aruba Central NetConductor underlay orchestration workflow.

A three-tier network identified as Seattle is used to illustrate this process.

Table of contents

Planning the Underlay

Note: Underlay Orchestration requires a minimum AOS-CX firmware version 10.12.

Before running the Underlay Orchestration workflow, all physical links between switches must be connected. The workflow automation determines the network topology based on these physical connections and completes the OSPF and VSX configurations accordingly. This includes VSX inter-switch links and a keepalive connection. Making these connections during switch deployment enables the automation to detect a redundant switch pair and provide the desired VSX configuration.

The Underlay Orchestration workflow requires two IP address pools. The pools are used to configure point-to-point OSPF links between switches in the fabric and to create two loopback interfaces on each switch. The loopback0 interface is used as the OSPF router ID and in-band management interface. The loopback1 interface is used as the VTEP source interface if an EVPN fabric is deployed next.

Pool NameAddress Range
Loopback IP Pool10.0.10.1/24
Routed Interface IP Pool10.10.15.1/24

Create a Central Group

All switches must be online and in the same group. Wireless gateways and APs may be in a different group; however, consider including them in the same group for ease of network management in a greenfield deployment.

For step-by-step instructions on creating a new group and adding devices to it, consult the Aruba Central section found earlier in this guide.

Configure the Underlay

Use this procedure to configure an OSPF campus using the Underlay Orchestration workflow in Central.

Step 1 In the Global dropdown, select the switch group. In this example, the group is SEACP-FAB.

Step 2 On the left menu, select Devices.

Step 3 Select Switches, then select Config.

Step 4 Under Routing, select Underlay Networks.

Step 5 In the Networks table, click the + (plus sign) at the top right.

Step 6 The Guided Setup for Underlay Network workflow appears. In the Network Type window, assign the following settings, and click Next.

  • Network Name: SEACP-Underlay
  • What type of network to configure?: Campus(3 tier L3 access)

Step 7 In the Structure window, assign the following settings and click Next.

  • On which devices the WAN gateways (site uplink) is connected?: Core Switches
  • Do you have WLAN gateway?: Yes, Connected to Service Aggregation Switches

Step 8 In the Device Assignment window, select the Core Switches of the network and click Next.

Step 9 In the Device Assignment window, select the WLAN Service Aggregation Switches for the network and click Next.

Step 10 In the Device Assignment window, select the Access Aggregation Switches for the network and click Next.

Step 11 In the Device Assignment window, select the Access Switches for the network and click Next.

Step 12 In the Configuration window, enter the following values or leave the default, then click Next:

  • Interface IPv4 subnet pool: 10.10.15.1/24
  • Loopback IPv4 subnet pool: 10.0.10.1/24
  • MTU size (bytes): Leave default
  • VSX-Pair Transit VLAN: Leave default
  • Use out-of-band management port for VSX keepalive: Leave unchecked
  • Use NTP servers: Slide to the right
    • Inherited from group
  • Use DNS servers: Slide to the right
    • Inherited from group

Step 13 In the Summary window, review the configuration details, then click Finish. Central immediately begins to configure the network.

Step 14 On the left menu, select Audit Log. Confirm the successful deployment of the underlay configuration by observing the log messages highlighted below.

Note: The Underlay Orchestration workflow deploys a Layer 3 access configuration. Access point VLANs must be created manually on the underlay access switches with an IP helper enabled to allow AP onboarding to Central using DHCP.


Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.