Dell PowerConnect W Clearpass 100 Software ArubaOS Integration Cheat Sheet - Page 18

Troubleshooting Tips

Page 18 highlights

ArubaOS + Amigopod Integration Cheet Sheet 14. Troubleshooting Tips Test device is not being redirected to the Amigopod Captive Portal: • Check DNS resolution as client will not be redirected if it can't resolve initially requested webpage. • Check the captiveportal policy and ensure traffic is permitted to the Amigopod IP Address for the redirect via HTTP or HTTPS. • Does the amigopod have a route back to the test client's address space - look at use of NAT, default gateway of Amigopod etc. Login process stalls and never receive RADIUS request from Aruba Controller in logs: • Check the Web Login page and ensure correct IP address for controller is configured • Check the captiveportal policy and ensure traffic is permitted to configured IP address of the controller in the step above Receiving error message in RADIUS Logs about unknown client: • Check the RADIUS NAS List and make sure there is an entry present that matches the IP address listed in the error message. Aruba Controller maybe using loopback instead of interface address as source for RADIUS traffic. • Make sure you restarted the RADIUS Server after you added the new RADIUS NAS entry for the Aruba controller. • Run test RADIUS authentication from the Aruba Controller to ensure basic connectivity using UDP 1812 / 1813. Receiving error message in RADIUS Logs about login incorrect • Check the username and password has been entered correctly - reset password if required. • Check that the shared secrets are the same on both Amigopod and ArubaOS - reset on both ends to be sure. • Run RADIUS debugger on Amigopod for deeper analysis of the transaction. Aruba Networks | 18

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

ArubaOS + Amigopod Integration Cheet Sheet
Aruba Networks |
18
14.
Troubleshooting Tips
Test device is not being redirected to the Amigopod Captive Portal:
Check DNS resolution as client will not be redirected if it can’t resolve initially
requested webpage.
Check the captiveportal policy and ensure traffic is permitted to the Amigopod IP
Address for the redirect via HTTP or HTTPS.
Does the amigopod have a route back to the test client’s address space – look at use
of NAT, default gateway of Amigopod etc.
Login process stalls and never receive RADIUS request from Aruba Controller in logs:
Check the Web Login page and ensure correct IP address for controller is configured
Check the captiveportal policy and ensure traffic is permitted to configured IP address
of the controller in the step above
Receiving error message in RADIUS Logs about unknown client:
Check the RADIUS NAS List and make sure there is an entry present that matches the
IP address listed in the error message. Aruba Controller maybe using loopback instead
of interface address as source for RADIUS traffic.
Make sure you restarted the RADIUS Server after you added the new RADIUS NAS
entry for the Aruba controller.
Run test RADIUS authentication from the Aruba Controller to ensure basic connectivity
using UDP 1812 / 1813.
Receiving error message in RADIUS Logs about login incorrect
Check the username and password has been entered correctly – reset password if
required.
Check that the shared secrets are the same on both Amigopod and ArubaOS – reset on
both ends to be sure.
Run RADIUS debugger on Amigopod for deeper analysis of the transaction.