Network Management

last person joined: 22 hours ago 

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

freeradius Aruba 3800 & Aruba 2930F

This thread has been viewed 8 times
  • 1.  freeradius Aruba 3800 & Aruba 2930F

    Posted Feb 20, 2017 05:14 PM

    Hey just looking into doing mac authentication Vlan assigning and wondering if anyone know if the  Aruba 3800 & Aruba 2930F support this they should do since they both support 802.1X but not sean much how to configure it. 

    Is it the same CLI as Hp Procurve 

     

    Thank you 



  • 2.  RE: freeradius Aruba 3800 & Aruba 2930F

    EMPLOYEE
    Posted Feb 20, 2017 05:20 PM
    Yes, you can assign VLAN ID or name via the standard IETF attributes.


  • 3.  RE: freeradius Aruba 3800 & Aruba 2930F

    EMPLOYEE
    Posted Feb 20, 2017 05:20 PM
    Yes, you can assign VLAN ID or name via the standard IETF attributes.


  • 4.  RE: freeradius Aruba 3800 & Aruba 2930F

    Posted Feb 20, 2017 05:36 PM

    Ok great, is is as simple as following configuration 

     

    http://www.brocade.com/content/html/en/deployment-guide/brcd-fastiron-08040-flexible-authentication-dp/GUID-46EEE36F-C512-40F7-A46C-494FDD5A6C51.html

     

     

    Can not find any documenation on Aruba 



  • 5.  RE: freeradius Aruba 3800 & Aruba 2930F

    EMPLOYEE
    Posted Feb 23, 2017 04:59 AM

    Most things you find on Provision OS will work on AOS-S (ArubaOS switches) as what was named Provision OS till the 15.x release is called ArubaOS starting with the 16.x release.

     

    You can get product documentation from the Network Information Library: http://h17007.www1.hpe.com/us/en/networking/library/index.aspx?cat=switches&subcat=aruba_3810

    .. where the HPE ArubaOS-Switch Access Security Guide will give you probably the needed information on assigning VLAN (but also dynamic ACLs, and other features) via RADIUS.

     

    As Tim mentioned, the 'default' method with IETF attributes (Tunnel-Type, Tunnel-Medium-Type, and Tunnel-Private-Group-ID) will work and is what most people will use. With the RFC4675 attributes Egress-VLANID or Egress-VLAN-Name you can even assign tagged VLANs in addition to the untagged VLAN.