ArubaOS 8.6.0.0Help Center
Uplink Routing using Next-hop Lists
If themanaged deviceuses policy-based routing to forward packets to a next-hop device, a next-hop list ensures that if the primary next-hop device becomes unreachable, the packets matching the policy can still reach their destination.ArubaOSnow also allows IPv6 next-hop lists in policy-based routing. For more information on next-hop configuration, seePolicy Based Routing.
Defining Next-hop Lists
The following procedure describes how to define a next-hop list:
1.In theManaged Networknode hierarchy, navigate to theConfiguration> Services> WANtab.
2.Expand theNext Hop Configurationaccordion.
3.(Optional) In theHealth check probe intervalfield, specify the probe interval, in seconds.
The default value is 10 seconds.
4.(Optional) In thePocket Burst per Probefield, specify the number of probes to be sent during the probe interval.
The default value is 5 probes.
5.Click + below theNextHop Liststable to open theNextHopsection that allows you to configure the following next-hop settings:
Table 1:Managed DeviceNext-Hop Settings
Parameter |
Description |
NextHop list name |
Add a name for the new next-hop list. NOTE:You cannot use the same name for both IPv4 and IPv6 next-hop lists. |
IP version |
Select eitherIPv4orIPv6from the drop-down list, which you want to assign for the new next-hop list. |
NextHops |
IPv4 or IPv6 address of the next-hop device or theID of theused by the next-hop device. If thegets an IPv4 address using, and the defaultis determined by the接口,IP is used as the next-hop IP address. Click+to open theAdd IPv4 NextHoppop-up window, if you selectedIPv4option in theIP versionfield. In theAdd IPv4 NextHoppop-up window, select one of the following radio buttons: IP— Enter the IPv4 address and priority of the next-hop device In theIP addressandPriorityfields respectively. DHCP— Enter theID and priority of the next-hop device In theVLAN IDandPriorityfields respectively. Click+to open theAdd IPv6 NextHoppop-up window, if you selectedIPv6option in theIP versionfield. In theAdd IPv6 NextHoppop-up window, enter the IPv6 address and priority of the next-hop device in theIPv6 addressandPriorityfields. Use the optionalPriorityfield to assign priority to next-hop device. The range is 1-255 and default value is 128. NOTE:You can configure a maximum of 16 next-hop devices for a next-hop list, and a maximum of 32 next-hop lists are currently supported. NOTE:You cannot configure IPv6 multicast, link-local, unspecified, loopback, andanycast addresses as IPv6 next-hop addresses. |
IPsec map name |
A next-hop list may require policy-based redirection of traffic to differenttunnels. Select anmap to redirect traffic throughtunnels. Click+to open theAdd New IPsec Mappop-up window. Select eitherUsing site-to-site IPSecorUsing IPSec Tunnel to VPNCoption from the drop-down list ofForward Settingsfield, and specify the priority in thePriorityfield. NOTE:For IPv6 address, onlyUsing site-to-site IPSecoption is supported underForward Settingsfield. If amanaged deviceterminates a secure tunnel on aconcentrator, you can issue thevpn-peer peer-maccommand on theconcentrator configuration to enable load balancing on secure uplinks between theconcentrator and amanaged device. The following example enables uplinks between amanaged devicewith theaddress 01:00:5E:00:00:FF and aconcentrator, this automatically enables load balancing: (host)[node](config) #vpn-peer peer-mac 01:00:5E:00:00:FF cert-auth factory-cert NOTE:If the peer device is an x86 server, then configure theaddress of the management interface of themanaged device. However, if the peer device is a hardware platform, you must provide theaddress of theinterface of themanaged device |
Preemptive-failover |
If preemptive failover is disabled and the highest-priority device on the next-hop list is disabled, the new primary next-hop device remains the primary even when the original device comes back online. |
6.ClickSubmit.
7.ClickPending Changes.
8.In thePending Changeswindow, select the check box.
9.ClickDeploy Changes.