ArubaOS 220.127.116.11 Help Center
Uplink Routing using Next-hop Lists
If the managed device uses 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. ArubaOS now also allows IPv6 next-hop lists in policy-based routing. For more information on next-hop configuration, see Policy Based Routing.
Defining Next-hop Lists
The following procedure describes how to define a next-hop list:
1. In the node hierarchy, navigate to the tab.
2. Expand the accordion.
3. (Optional) In the field, specify the probe interval, in seconds.
The default value is 10 seconds.
4. (Optional) In the field, specify the number of probes to be sent during the probe interval.
The default value is 5 probes.
5. Click + below the table to open the section that allows you to configure the following next-hop settings:
Table 1: Managed Device Next-Hop Settings
Add a name for the new next-hop list.
You cannot use the same name for both IPv4 and IPv6 next-hop lists.
or from the drop-down list, which you want to assign for the new next-hop list.
IPv4 or IPv6 address of the next-hop device
or the ID of the used by the next-hop device. If the gets an IPv4 address using , and the default is determined by the interface, the IP is used as the next-hop IP address.
to open the pop-up window, if you selected option in the field. In the pop-up window, select one of the following radio buttons:
— Enter the IPv4 address and priority of the next-hop device In the and fields respectively.
ID and priority of the next-hop device In the and fields respectively.
— Enter the
to open the pop-up window, if you selected option in the field.
pop-up window, enter the IPv6 address and priority of the next-hop device in the and fields.
Use the optional
field to assign priority to next-hop device. The range is 1-255 and default value is 128.
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.
You cannot configure IPv6 multicast, link-local, unspecified, loopback, and anycast addresses as IPv6 next-hop addresses.
A next-hop list may require policy-based redirection of traffic to different tunnels. Select an map to redirect traffic through tunnels.
to open the pop-up window. Select either or option from the drop-down list of field, and specify the priority in the field.
For IPv6 address, only option is supported under field.
If a managed device terminates a secure tunnel on a concentrator, you can issue the command on the concentrator configuration to enable load balancing on secure uplinks between the concentrator and a managed device.
The following example enables uplinks between a managed device with the address 01:00:5E:00:00:FF and a concentrator, this automatically enables load balancing:
(host)[node](config) #vpn-peer peer-mac 01:00:5E:00:00:FF cert-auth factory-cert
If the peer device is an x86 server, then configure the address of the management interface of the managed device. However, if the peer device is a hardware platform, you must provide the address of the interface of the managed device
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. Click Submit.
7. Click .
8. In the window, select the check box.
9. Click .