IPsec Tunnel Failures
The following behaviors can cause an IPsec tunnel creation failure:
• Time
The time in the switch has to be valid and correct. Ensure that NTP configuration is set up on switch and on
the controller where the tunnel is terminating.
• Authentication
The switch MAC addresses for both members must be added to the Aruba controller whitelist.
• Controller IP
The controller IP must be reachable from the switch.
• Inner IP pool
Ensure the inner IP pool is configured on the controller. Tunnel establishment is not successful, if the pool is
full.
• Static Route
There must not be any conflicting static route in the system for the AirWave IP configured.
• License
The controller must have sufficient license to support IPsec tunnels.
IPsec tunnel to secondary controller
ArubaOS-Switch assists support for IPsec tunnel between switch and the Aruba Controller (VPN concentrator) to
carry the switch generated traffic to multiple services behind the Aruba Controller. The services include AirWave
management station, ClearPass, DNS, Syslog, and so on.
IPsec tunnel needs a backup support for IPsec session failure. If the existing IPsec session is lost, the switch is
able to establish a new IPsec tunnel session with a backup controller (secondary controller).
Backup controller support for IPsec tunnel
The switch supports two controllers with all the services such as ClearPass, Syslog, DNS, and AirWave. In such
scenarios, a controller functions as a backup controller.
1.
aruba-vpn
is modified to support backup controller IP.
aruba-vpn type amp peer-ip
<IP_addr>
backup-peer-ip
<IP_addr>
no aruba-vpn type amp peer-ip
<IP_addr>
backup-peer-ip
<IP_addr>
switch(config)#
aruba-vpn type amp peer-ip 171.0.0.1
backup-peer-ip Configure the Aruba VPN backup IP address.
tos Configure the Aruba VPN tos value.
ttl Configure the Aruba VPN ttl value.
switch(config)#
aruba-vpn type amp peer-ip 171.0.0.1 backup-peer-ip 171.0.0.3
2.
When the switch is configured with both the primary and backup controllers, the switch will establish IPsec
tunnel connection with primary controller.
3.
Switch initiates a new IPsec session with either primary or backup controller once "Dead Peer Detection" event
is triggered for existing IPsec session.
4.
Switch retries establishing IPsec session with both primary and backup controllers alternatively until a
successful IPsec handshake.
316
Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08