Dell PowerConnect W Clearpass 100 Software ArubaOS Integration Guide - Page 49

Troubleshooting Tips, Aruba controller.

Get Dell PowerConnect W Clearpass 100 Software PDF manuals and user guides View all Dell PowerConnect W Clearpass 100 Software manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

Amigopod and ArubaOS Integration Application Note Chapter 6: Troubleshooting Tips This chapter provides basic troubleshooting steps to use for specific issues. If the test device is not being redirected to the Amigopod captive portal:  Check the DNS resolution because the client will not be redirected if it cannot resolve the initially requested webpage. Command line tools such as nslookup and ping can be used.  Check the initial role that is assigned to the guest AAA profile and ensure that traffic is permitted to the Amigopod IP address for the redirect via HTTP or HTTPS via an appropriate policy.  Verify that the Amigopod has a route back to the address space of the test client. Look at how NAT and the default gateway of Amigopod are referenced as part of your troubleshooting steps. If the login process stalls and the logs show that no RADIUS request was received from the Aruba controller:  Check the web login page and ensure that the correct IP address for controller is configured.  Check the captive portal policy and ensure that traffic is permitted to the configured IP address of the controller. If you receive an error message in the RADIUS logs about an unknown client:  Check the RADIUS NAS list and ensure that it has an entry that matches the IP address listed in the error message. The Aruba controller may be using loopback instead of the 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. If you receive an error message in the RADIUS logs about an incorrect login:  Check that the username and password has been entered correctly. Reset the password if necessary.  Check that the shared secrets are the same on the Amigopod and ArubaOS. Reset the keys on both ends to be sure.  Run RADIUS debugger on Amigopod for deeper analysis of the transaction. Aruba Networks, Inc. Troubleshooting Tips | 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
Aruba Networks, Inc.
Troubleshooting Tips
|
49
Amigopod and ArubaOS Integration
Application Note
Chapter 6: Troubleshooting Tips
This chapter provides basic troubleshooting steps to use for specific issues.
If the test device is not being redirected to the Amigopod captive portal:
Check the DNS resolution because the client will not be redirected if it cannot resolve the initially
requested webpage. Command line tools such as nslookup and ping can be used.
Check the initial role that is assigned to the guest AAA profile and ensure that traffic is permitted
to the Amigopod IP address for the redirect via HTTP or HTTPS via an appropriate policy
.
Verify that the Amigopod has a route back to the address space of the test client. Look at how
NAT and the default gateway of Amigopod are referenced as part of your troubleshooting steps.
If the login process stalls and the logs show that no RADIUS request was received from the Aruba
controller:
Check the web login page and ensure that the correct IP address for controller is configured
.
Check the captive portal policy and ensure that traffic is permitted to the configured IP address
of the controller
.
If you receive an error message in the RADIUS logs about an unknown client:
Check the RADIUS NAS list and ensure that it has an entry that matches the IP address listed in
the error message. The Aruba controller may be using loopback instead of the 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.
If you receive an error message in the RADIUS logs about an incorrect login:
Check that the username and password has been entered correctly
.
Reset the password if
necessary
.
Check that the shared secrets are the same on the Amigopod and ArubaOS
.
Reset the keys on
both ends to be sure.
Run RADIUS debugger on Amigopod for deeper analysis of the transaction.