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

Link aggregation 7005 vs. 54xxzl

This thread has been viewed 0 times
  • 1.  Link aggregation 7005 vs. 54xxzl

    Posted Mar 15, 2017 01:11 PM

    Hi there,

    I configured in a testlab our 7005 with ArubaOS 8.0.1.0 57205 (is there any newer out there?) with some AP315 and enterprise-WPA2 with RADIUS-Auth.

    Everything is fine so far. Now I want to get this into production and for that I wish to aggregate all 4 Gigabit-ports to the main switch HPE 5412zl. 

    Setting up a static trunk does not work at all.

    Using LACS I was not really able to get it up and running again:

    I can manage the controller, the APs do connect to master, they do broadcast the SSID - but connecting to that WLAN takes more than 10s and after beeing connected there is not really traffic flowing.

     

    The configuration is as follows:

    interface gigabitethernet 0/0/0

        description "GE0/0/0"

        trusted

        trusted vlan 1

        no poe

        no spanning-tree

    !

     

    interface gigabitethernet 0/0/1

        description "GE0/0/1"                          

        trusted

        trusted vlan 1

        no poe

        no spanning-tree

    !

     

    interface gigabitethernet 0/0/2

        description "GE0/0/2"

        trusted

        trusted vlan 1

        no poe

        no spanning-tree

    !

     

    interface gigabitethernet 0/0/3

        description "GE0/0/3"

        trusted

        trusted vlan 1

        no poe

        no spanning-tree

    !

                                                       

    interface port-channel 0

        add gigabitethernet 0/0/0

        add gigabitethernet 0/0/1

        add gigabitethernet 0/0/2

        add gigabitethernet 0/0/3

        trusted

        trusted vlan 1

        switchport trunk allowed vlan 1-4094

    !

     

    interface vlan 1

        ip address 192.168.0.254 255.255.254.0

    !

     

    !

    no uplink wired vlan 1

    no uplink enable

    !

    ip default-gateway 192.168.0.99

    ip nexthop-list load-balance-gateways

     

    I did manually set "lacp group 0 mode active" to the gigabit-interfaces which does not made any difference.

     

    On 54xxzl-side there is only defined "LACP status "Passive""

     

    Could someone give an advice, please?

    Thanks!



  • 2.  RE: Link aggregation 7005 vs. 54xxzl

    Posted Mar 15, 2017 03:10 PM
    The way you currently configured is to use static

    If you want to use lacp on the controller side you need configure it this way:

    interface gigabitethernet 0/0/0
    trusted
    trusted vlan "VLANS"
    lacp timeout short
    lacp group 0 mode active
    !
    interface gigabitethernet 0/0/1
    trusted
    trusted vlan "VLANS"
    lacp timeout short
    lacp group 0 mode active
    !
    interface gigabitethernet 0/0/2
    trusted
    trusted vlan "VLANS"
    lacp timeout short
    lacp group 0 mode active
    !
    interface gigabitethernet 0/0/3
    trusted
    trusted vlan "VLANS"
    lacp timeout short
    lacp group 0 mode active
    !

    interface port-channel 0
    trusted
    trusted vlan "VLANS"
    switchport mode trunk
    switchport trunk allowed vlan "VLANS"


  • 3.  RE: Link aggregation 7005 vs. 54xxzl
    Best Answer

    Posted Mar 15, 2017 04:03 PM

    Hi Victor,

    thank you for your input.

     

    Meanwhile the only thing I did is rebooting the 7005 - and now config is shown like this:

     

    interface gigabitethernet 0/0/3

        description "GE0/0/3"

        trusted

        trusted vlan 1

        no poe

        no spanning-tree

        lacp group 0 mode active

    !

     

    interface port-channel 0

        trusted

        trusted vlan 1

        switchport mode trunk

        switchport trunk allowed vlan 1-4094

     

    (OK, the "switchport mode trunk" for port channel 0 I added just right now).

     

    So why my config does not change reproduceable by 

    #write memory

    Do I really have to reboot the whole controller?

     

    And I was wondering, too, that after my initial configuration via GUI just eth 0+1 did show "mode: PC-0" - eth 2+3 still were shown as "access".

    Even after removing them from PC-0 and rejoining I had to change the state via CLI.

    So the question is: is there any newer realease of ArubaOS than mine?

     

    Thanks again - F.One

    I cannot confirm that the things are now working as expected because I´m at home now and just connected via VPN.