Network Management

last person joined: 9 hours ago 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Back to discussions
Expand all | Collapse all

RADIUS Auth issues in Airwave when not using RADIUS auth?

This thread has been viewed 0 times

  • 1.  RADIUS Auth issues in Airwave when not using RADIUS auth?

    Posted Nov 06, 2012 08:58 AM
      |   view attached

    Good Morning,

     

    I seem to have stumbled upong the following errors in Airwave but we are not using RADIUS authentication but only RADIUS Accounting.

     

    I have attached the screenshot.

     

    Any idea what may cause this ?

    The controller is a 3200 running on 6.1.3.3


    #3200


  • 2.  RE: RADIUS Auth issues in Airwave when not using RADIUS auth?

    EMPLOYEE
    Posted Nov 06, 2012 02:20 PM

    It looks like your controller is passing on client auth failure messages.  This can be resolved by disabling the unneeded traps from the controller:

     

    # ssh admin@controller.ip

    # en

    # conf t

    # snmp-server trap disable wlsxNUserAuthenticationFailed

    # snmp-server trap disable wlsxUserAuthenticationFailed

    ctrl+z

    # wr mem

     

    I believe these are the two that need to be disabled, you can double-check from the list that's in the Aruba-AirWave Best Practices Guide (http://support.arubanetworks.com/DOCUMENTATION/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=8053).



  • 3.  RE: RADIUS Auth issues in Airwave when not using RADIUS auth?

    Posted Nov 06, 2012 02:26 PM

    I guess this would work as we use external captive portal authentication.

     

    I just don't want to disable something that we can use for troubleshooting later on



  • 4.  RE: RADIUS Auth issues in Airwave when not using RADIUS auth?

    EMPLOYEE
    Posted Nov 06, 2012 04:35 PM

    The traps won't help much for troubleshooting since the output is nonsense (controller is passing back several invalid NULL MAC addresses).  In any event, these traps can always be re-enabled later on, disabling for now will just help decrease the noise until you can resolve the issue that the controller sees failed authentications for the NULL MAC address several times over.  It could be that your external captive portal authentication is either blocking the MAC address or using another distinct field to define different clients. May be worth it to open an Aruba TAC case to troubleshoot.