Wired Intelligent Edge

 View Only
last person joined: 2 days ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

Aruba 6100 cx - LAG Switche verbinden

This thread has been viewed 13 times
  • 1.  Aruba 6100 cx - LAG Switche verbinden

    Posted 7 days ago

    Moin Alle,

    irgendwie stehe ich gerade auf dem Schlauch. Meine Switche funktionieren gut (nur über 1 Kabel verbunden), jetzt kommt ein neues Thema, LAGs. Da bin ich echter Anfänger.
    Ich möchte an meinem bestehenden Aruba 6100 einen zweiten Switch anbinden. Switch 1 die Ports 50 und 52, an den neuen Switch Aruba 6100 Ports 25 und 26.
    Leider komme ich in der GUI und auf der Konsole da nicht weiter. Es sollen auch mehrere VLan's durchgereicht werden: VLan's: 100,200,300
    Kann mir da einer helfen, muss ich auf beiden Switche die gleichen Einstellungen machen. Wie funktioniert das dann mit Spanning-Tree?

    Bin für jeden Tip dankbar.

    Gruß, Tom.



  • 2.  RE: Aruba 6100 cx - LAG Switche verbinden

    MVP GURU
    Posted 6 days ago

    Configure a Layer 2 dynamic aggregation group:

    switch# config
    switch(config)#
    switch(config)# interface lag <ID>
    switch(config-lag-if)# no shutdown
    switch(config-lag-if)# description LAG-to-Peer-Switch-B
    switch(config-lag-if)# lacp mode active
    switch(config-lag-if)# lacp rate slow
    switch(config-lag-if)# vlan trunk native <VLAN-ID-of-Port-VID> (for example: vlan trunk native 1) <- see note below to force the native to be tagged
    switch(config-lag-if)# vlan trunk allow <VLAN-IDs-of-Allowed-VLANs> (for example: vlan trunk allow 1,100,200,300 <- 1 is allowed as "untagged" on the LAG, 100, 200, 300 are allowed as "tagged" on the LAG)
    switch(config-lag-if)# exit
    switch(config)#
    switch(config)# write memory
    switch(config)# copy running-configuration startup-configuration

    Assign physical interface(s) to the above create LAG:

    switch(config)#
    switch(config)# interface 1/1/50
    switch(config-if)# lag <ID> (see above for the the used LAG ID <- LAG IDs used on the two peer switches could be the same - say, as example, lag 10 on peer A and lag 10 on peer B - or not - say, as example, lag 10 on peer A and lag 20 on peer B - no particular restrictions here in selecting free LAG IDs on each switch apart picking up a LAG ID from the supported range)
    switch(config-if)# no shutdown
    switch(config-if)# exit
    switch(config)# interface 1/1/52
    switch(config-if)# lag <ID>
    switch(config-if)# no shutdown
    switch(config-if)# exit
    switch(config)#
    switch(config)# write memory
    switch(config)# copy running-configuration startup-configuration

    To the same on corresponding peer switch B.

    A show running-config should then show on one of the two peer switches (example on peer Switch A with the lag 10 as LAG ID and four VLANs allowed: 1, 100, 200 and 300):

    ...
    interface lag 10
    no shutdown
    description LAG-to-Peer-Switch-B
    vlan trunk native 1 (or vlan trunk native 1 tag)
    vlan trunk allowed 1,100,200,300
    lacp mode active
    lacp rate slow
    ...
    interface 1/1/50
    no shutdown
    lag 10
    interface 1/1/52
    no shutdown
    lag 10
    ...

    A show lacp aggregates then should output something like that on the peer switch A:

    Aggregate name  : lag10
    Interfaces      : 1/1/50 1/1/52
    Peer interfaces : 1/1/25 1/1/26
    Heartbeat rate  : Slow
    Hash            : l3-src-dst
    Aggregate mode  : Active

    You can eventually allow "tagged-only" VLAN IDs to cross the interlink between the two peer switches and so declaring a "vlan trunk native 1 tag" instead of declaring a "vlan trunk native 1" only: in this way the VLAN 1 - or whatever VLAN ID you decide to be the PVID/native VLAN on this interlink - is also transported tagged between the two peer switches along with the other VLANs (100, 200 and 300). Adapt to your configuration/requirements.




  • 3.  RE: Aruba 6100 cx - LAG Switche verbinden

    Posted 6 days ago

    Hi, vielen Dank für die Hilfe. 
    Ich hab das genauso übertragen und alles funktioniert.

    Danke.

    Gruß, Tom.




  • 4.  RE: Aruba 6100 cx - LAG Switche verbinden

    MVP GURU
    Posted 6 days ago

    Gut gemacht Tom! Gruß, Davide.