Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Changed controller IP and now radius doesn't work

This thread has been viewed 1 times

  • 1.  Changed controller IP and now radius doesn't work

    Posted May 16, 2014 03:49 PM

    I changed my controller IP to a different vlan/interface.  I rebooted the controller.  I also changed the NAS IP to be the new IP/VLAN, and added a new NPS client on the Windows NPS Server, but authentication fails.  I retyped the passwords 3 times now.  I deleted the new NPS client, and editec the old client with the updated controller IP.  I have tried deleting all NPS clients and recreating them.

     

    Still authentication test fails.



  • 2.  RE: Changed controller IP and now radius doesn't work

    Posted May 16, 2014 03:52 PM
    Do ?show ip radius source-interface?. Is that the IP you are expecting you RADIUS server to see? If not, you can change it using the ?ip radius source-interface vlan x? command from config mode.


  • 3.  RE: Changed controller IP and now radius doesn't work

    Posted May 16, 2014 04:03 PM

    That output is the new controller IP/VLAN, so that looks good.



  • 4.  RE: Changed controller IP and now radius doesn't work

    EMPLOYEE
    Posted May 16, 2014 04:07 PM

    When you are trying to use the aaa test command, what output are you getting - failed or timed out?



  • 5.  RE: Changed controller IP and now radius doesn't work

    Posted May 16, 2014 04:10 PM

    Authentication Failed



  • 6.  RE: Changed controller IP and now radius doesn't work
    Best Answer

    EMPLOYEE
    Posted May 16, 2014 04:13 PM

    Good!  That means that the controller and RADIUS server are correct.  The user/credentials failed.  

     

    Can you try MSCHAPv2 vs PAP?  That may be the issue.