Quanta LB6M LACP trunk unable to pass traffic with vlans

Discussion in 'Networking' started by gr8ape, Oct 31, 2016.

  1. gr8ape

    gr8ape Member

    Joined:
    Jun 15, 2015
    Messages:
    41
    Likes Received:
    4
    Hey all!

    I hope someone has managed to figure this out as it is perplexing me. I've tried setting up the LACP and VLAN trunking as per Quanta LB6M (10GbE) -- Discussion , but for some reason, anything but the management vlan refuses to pass. I can ping between the VLAN connections that are native to the switch, but if I try to get to another switch with that VLAN, it won't work.

    My switches are 5520 and LB6M. Any suggestions? Thanks!
     
    #1
  2. Drewy

    Drewy Member

    Joined:
    Apr 23, 2016
    Messages:
    168
    Likes Received:
    23
    Mine works fine. Got multiple vlans running over multiple lag/lacp trunks.
    Are you adding the port-channels to the vlans?
     
    #2
  3. GuybrushThreepwood

    Joined:
    Aug 2, 2015
    Messages:
    70
    Likes Received:
    26
    Paste your config here?
     
    #3
  4. gr8ape

    gr8ape Member

    Joined:
    Jun 15, 2015
    Messages:
    41
    Likes Received:
    4
    Fixed it, turns out I forgot to create a firewall rule to allow traffic on that VLAN.

    3 days down the drain on that one...

    For anyone in the future, here is my config:

    Code:
    (FASTPATH Routing) #show running-config
    !Current Configuration:
    !
    !System Description "Quanta LB6M, 1.2.0.18, Linux 2.6.21.7"
    !System Software Version "1.2.0.18"
    !System Up Time          "0 days 1 hrs 7 mins 45 secs"
    !Additional Packages     FASTPATH QOS
    !Current SNTP Synchronized Time: Nov  1 21:20:08 201 UTC
    !
    network protocol none
    serviceport protocol none
    serviceport ip <IP> <NM> <GW>
    vlan database
    vlan 222
    vlan name 222 "storage"
    exit 
    ip ssh server enable
    ip ssh protocol 2 
    no ip telnet server enable
    configure
    sntp client mode unicast
    sntp client port 123
    ! sntp server status is Success
    sntp server "128.227.205.3" 
    ! sntp server status is Other
    sntp server "130.207.244.240" 2 
    aaa authentication enable "enableList" enable
    line console
    exit
    line telnet
    exit
    line ssh
    exit
    spanning-tree configuration name "<MAC>"
    port-channel name 1/1 Trunk2Backbone
    interface 0/25
    addport 1/1
    exit
    interface 0/26
    addport 1/1
    exit
    interface 0/27
    addport 1/1
    exit
    interface 0/28
    addport 1/1
    exit
    !
    interface 0/7
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/8
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/10
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/11
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/12
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/13
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/14
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/16
    vlan pvid 222
    vlan participation exclude 1
    vlan participation include 222
    exit
    interface 0/25
    port lacptimeout actor short
    port lacptimeout partner short
    description 'LAG Port for Trunk to Backbone'
    no lacp actor admin state longtimeout
    no lacp partner admin state longtimeout
    exit
    interface 0/26
    port lacptimeout actor short
    port lacptimeout partner short
    description 'LAG Port for Trunk to Backbone'
    no lacp actor admin state longtimeout
    no lacp partner admin state longtimeout
    exit
    interface 0/27
    port lacptimeout actor short
    port lacptimeout partner short
    description 'LAG Port for Trunk to Backbone'
    no lacp actor admin state longtimeout
    no lacp partner admin state longtimeout
    exit
    interface 0/28
    port lacptimeout actor short
    port lacptimeout partner short
    description 'LAG Port for Trunk to Backbone'
    no lacp actor admin state longtimeout
    no lacp partner admin state longtimeout
    exit
    interface 1/1
    description 'Trunk to Backbone'
    no port-channel static
    vlan acceptframe vlanonly
    vlan participation include 222
    vlan tagging 1,222
    exit
    router rip
    exit
    router ospf
    exit
    exit
    
     
    #4
    Last edited: Nov 3, 2016
  5. Drewy

    Drewy Member

    Joined:
    Apr 23, 2016
    Messages:
    168
    Likes Received:
    23
    Your config looks a little different to mine and my switch is on an earlier firmware version, but if it helps here is my working config:

    interface 0/8

    no auto-negotiate

    addport 1/1

    exit

    interface 0/14

    no auto-negotiate

    addport 1/1

    exit

    interface 0/25

    addport 1/2

    exit

    interface 0/26

    addport 1/2

    exit

    interface 0/27

    addport 1/2

    exit

    interface 0/28


    --More-- or (q)uit


    addport 1/2

    exit

    interface 0/19

    no auto-negotiate

    addport 1/3

    exit

    interface 0/20

    no auto-negotiate

    addport 1/3

    exit

    !

    interface 0/19

    description 'LAG to office'

    exit

    interface 0/20

    description 'LAG to office'

    exit

    interface 1/1

    description 'LAG to freenas'

    no port-channel static

    exit

    interface 1/2

    description 'lag to 1gb switch'

    spanning-tree edgeport


    --More-- or (q)uit


    vlan participation include 10,14,20

    vlan tagging 10,14,20

    exit

    interface 1/3

    description 'LAG to office'

    no port-channel static

    spanning-tree edgeport

    vlan participation include 10,14,20

    vlan tagging 10,14,20

    exit

    router rip

    exit

    router ospf

    exit

    exit


    For what it's worth, I spent ages "trying" to get the lb6m to pass vlan traffic over lag/lacp. In my case it wasn't the lb6m that was the problem it was the switch before the lb6m.
     
    #5
  6. David Yee

    David Yee New Member

    Joined:
    May 9, 2017
    Messages:
    1
    Likes Received:
    0
    Hi there,
    I am having a similar issue with vlan traffic not passing through to another switch and i think my logic on the routing seems to be wrong.
    System: T3040-LY3 Runtime Code 1.4.10.00 Linux 2.6.35
    vlan 3001; native to all ports; allowed at all ports; untagged to all ports except port 48 (tagged).
    port 48 is the uplink to another switch which also has vlan 3001.
    Over at the discuss of "Quanta LB6M (10GbE) -- Discussion" some suggested "trunk port", but my switch do not have an "trunk port" after "switchport" command. Instead there is this "vtp" command but with a vlan limitation of 1005.
    Currently traffic only goes through the management network.
    Could you guys advise? Thank you
     
    #6
    Last edited: May 11, 2017
  7. CKat

    CKat New Member

    Joined:
    May 20, 2017
    Messages:
    14
    Likes Received:
    1


    Hello gr8ape -- Hopefully you can help out here... I am stuck in the same situation as you were. I am just trying to pass the VLAN traffic but none is going through - only default goes through.

    • What are the commands to allow traffic for say vlan 100 for interface 1/10 for the firewall?
    • Do I need to do anything specific for the uplink port to pass the traffic to all interfaces? I am using port 44 (Ethernet port) to link back to the master switch which is passing the vlan traffic.
    • What is the difference between interface 0/10 and 1/10 for example?
     
    #7
  8. CKat

    CKat New Member

    Joined:
    May 20, 2017
    Messages:
    14
    Likes Received:
    1

    Did you figure out how to get other VLAN traffic to pass through? I am stuck with same issue.
     
    #8
  9. djbon2112

    djbon2112 New Member

    Joined:
    Nov 24, 2013
    Messages:
    24
    Likes Received:
    6
    I'm using your configuration exactly, and specifically the `no port-channel static` to make my 802.3ad LACP work properly; without it, the port-channels really don't pass traffic (no firewalling or anything to get in the way). But I'm curious if you or anyone else has run into the following when trying to create more than 8 dynamic port channels?

    Code:
    (s2) (Interface 1/9)#no port-channel static
    
    1/9
    Unable to convert static Port-channel to Dynamic.
    Maximum allowable dynamic Port-channels (8) already present in the system.
    
    
    I've got 9 total: one of the four 1G ports, then eight dual-pair 10G ports. This happens configuring the last. I'm on firmware 1.2.0.18, and this option seems needed for the LACP as mentioned but having a limit of 8 seems quite arbitrary. If there's another way around this (such as LACP with a static port-channel? though that doesn't work when I try it) that would also work.

    Version info:
    Code:
    System Description............................. Quanta LB6M, 1.2.0.18, Linux
                                                    2.6.21.7
    Machine Type................................... Quanta LB6M
    Machine Model.................................. LB6M
    Serial Number.................................. QTFCRWXXXXXXX
    FRU Number..................................... 1LB6BZZ0STJ
    Part Number.................................... BCM56820
    Maintenance Level.............................. A
    Manufacturer................................... 0xbc00
    Burned In MAC Address.......................... 04:7D:7B:XX:XX:XX
    Software Version............................... 1.2.0.18
    Operating System............................... Linux 2.6.21.7
    Network Processing Device...................... BCM56820_B0
    
     
    #9
  10. djbon2112

    djbon2112 New Member

    Joined:
    Nov 24, 2013
    Messages:
    24
    Likes Received:
    6
    Bumping this thread in the hopes that someone has seen this and knows a resolution. I'm getting to the point where I might want a 9th LACP group and this has become a blocker.

     
    #10
Similar Threads: Quanta LB6M
Forum Title Date
Networking Quanta lb6m How To Stack? Wednesday at 6:26 AM
Networking Turbocharged quanta lb6m 10GB issue Nov 5, 2019
Networking SFP+ 10gbase-T on turbocharged quanta lb6m Nov 3, 2019
Networking Quanta LB6M / TurboIron 24x slow transfers Apr 4, 2019
Networking 2 x interconnected Quanta LB6M won't forward tagged VLAN traffic over LAG Mar 11, 2019

Share This Page