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.
Expand all | Collapse all

Aruba controller multiple ssid/vlans

This thread has been viewed 12 times
  • 1.  Aruba controller multiple ssid/vlans

    Posted Apr 17, 2019 06:41 PM

    hello guys,

    i've got my hands on 7205 controller and some ap and i'm trying to lab some basic stuff up since im new to aruba

    what im trying to achieve based on the network below is:

    -configure the two controller ports as tagged and portchannel to the core switch

    -configure three ssids with different subnets/vlans, other than the controller management VLAN/SUBNET

    -im not using the management port, so can we just receive the management traffic just on the mentioned two ports ?

    - i want to make the core switch as the gateway for all ssid subnet

     

     

    i've managed to configure one ssid on the same management vlan I configure when seting up the controller , but when i'm trying another ssid with another VLAN it just wont work (i configure the VLAN ID- do i need anything else for that to work ? SVI is already configured at the switch)

    of course im missing something and i'm looking for guidance

     

    thanks in advance

    top.jpg



  • 2.  RE: Aruba controller multiple ssid/vlans

    Posted Apr 17, 2019 06:47 PM

    i forgot to mention that i'm using arubaos 8.4



  • 3.  RE: Aruba controller multiple ssid/vlans

    EMPLOYEE
    Posted Apr 18, 2019 09:28 AM

    You want to configure your interfaces at the switch level of the controller.  First type "show configuration node-hierarchy" to see the path you would need to configure your device directly.  Next, "cd" to the path of your Aruba controller that you want to configure, type "config t" and configure the port that you would have connected as a trunk:

     

    config t

    vlan x (first vlan)

    vlan y (second vlan)

    vlan z (third vlan)

    interface gigabitetherne0/0/0 (or whatever is the controller uplink interface)

    switchport mode trunk

    switchport trunk native vlan <native vlan number>

    switchport allowed trunk vlan all

    exit 

    write mem

     

    That will configure gigabitethernet0/0/0 on your controller as a trunk, make the native vlan match the native VLAN on the switch it is connected to and allow the vlans that you created for your wlans.

     

    Please let me know if that doesn't work.