Velocloud Integration
This document describes the steps to integrate VeloCloud SD-WAN Edge appliances, in High Availability (HA) configuration, with the Nile Service Block (NSB). The desired result is a seamless integration between the Nile Access Service and the customer’s extended network, and thus with the Internet.
The VeloClound appliances require manual configuration; no configuration of Nile NSB is necessary.
- Four unique /30 Subnets – To implement a High-Definition and an Always-On service, the setup uses Equal Cost Multi-Path (ECMP) routing to configure four point-to-point links, to provide Layer 3 transit between the NSB and the VeloCloud Edge appliances.
- Administrative access to the VeloCloud Edge appliances.
- The VeloCloud edge appliance cannot do static route with ECMP routing, so this guide uses OSPF for the L3 routing between the Nile gateways and the VeloCloud Edge appliances.
Both Nile gateways are active-active devices. It takes four unique ports to connect to the upstream edges (two each). VeloCloud is in Active/Standby mode; it requires 2 unique ports on the active and 2 unique ports on the standby appliance.
GE1 | VeloCloud HA Link |
GE3, GE4 | WAN Interfaces |
GE5, GE6, SFP1, SFP2 | LAN Interfaces |
- Log into you VeloCloud Orchestrator
- Navigate to Profiles
- Click on the Branch Profile which is assigned to the Branch Edge that we are going to configure in this setup.
- Navigate to OSPFv2 and enable it, as shown below.
- Log into you VeloCloud Orchestrator
- Navigate toEdges
- Select your site-specific Edge Device
- Click onConfigure
- Navigate toInterfaces
- Click on GE3
This example uses GE3 as the WAN Interfaces. It’s assumed you have two WAN providers
- In the IPv4 Settings
- Scrolling down, set the
- Click the
If you have a second WAN (Internet) interface, repeat the same steps for that interface as well. Use GE4 for the second WAN Interface.
- Navigate to
- Capability: if the Interface is in switched mode, change it to a routed port via the drop-down list.
- Once you have selected the routed port, uncheck the checkboxes
- IP Address: provide the IPv4 IP address to the interface. It is typically a /30 subnet.
- Click on the
- Click the
- In the
- On the same LAN interface configuration (GE3), click on
- Keep the default settings as they are.
- Click on
- Configure the settings as shown below
This configuration blocks the appliances from learning a default route inbound, and allows everything else. The VeloCloud Edge appliances learns all the NSB and user subnets as they are advertised by the Nile Gateways.
- Click onInbound Route Learning
- Configure the settings as shown below
The VeloCloud Edge appliances advertise a default route to the Nile GW. This setting attracts all traffic towards itself.
- Repeat the above same steps for GE6, SFP1, and SFP2 LAN side interfaces. Make sure the /30 subnets are unique for each of these LAN side interfaces.