2 x interconnected Quanta LB6M won't forward tagged VLAN traffic over LAG

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

mailinglists

New Member
Mar 3, 2017
19
0
1
44
Hi guys,

I have two Quanta LB6M connected together in LAG with LACP.
Only the pvid (default) VLAN traffic is getting passed through their inter connection (LAG 1/1), all other VLANs work only on specific switch, do not get relayed.

Can you share your config, if you have it working?
 
Last edited:

YueLuo

New Member
Apr 5, 2017
7
0
1
37
Guangzhou China
How did you configure your LAG? Did you add vlan tag?
Do something like this on both switches:
interface 1/1
vlan participation include 2(,3,...)
vlan tagging 1,2(,3...)
 

mailinglists

New Member
Mar 3, 2017
19
0
1
44
Thank you for reply.

Current config.

first node:
Code:
interface 1/1
description 'Port-channel na XXXXX'
no port-channel static
port-channel load-balance 6
no spanning-tree port mode
mtu 9216
vlan pvid 113
vlan participation exclude 1
vlan participation include 113,600,666-667
vlan tagging 600,666-667
exit
other node:
Code:
interface 1/1
description 'Port-channel na XXXXX'
no port-channel static
port-channel load-balance 6
no spanning-tree port mode
mtu 9216
vlan pvid 113
vlan participation exclude 1
vlan participation include 113,600,666-667
vlan tagging 600,666-667
exit
Do you see a problem with it?
 

YueLuo

New Member
Apr 5, 2017
7
0
1
37
Guangzhou China
How did you configure the non-LAG interfaces ?
If you are connecting to end-host devices (PC, printer, etc), just do "vlan participation include xxx" for each interface, no need to set vlan tag or pvid.
 

mailinglists

New Member
Mar 3, 2017
19
0
1
44
Clients are 802.1q aware hypervisors. Tagged vlan traffic works among-st other hosts on the same switch, if just fails to traverse internal bond to the other switch. :-( I do not understand why not. Config seems fine to me. :-/

Here is the config for client port:
Code:
interface 0/4
no spanning-tree port mode
mtu 9216
vlan pvid 113
vlan ingressfilter
vlan participation exclude 1
vlan participation include 113,600,667
vlan tagging 600,667
exit
Here is the relevant part for adding ports to LAG:
Code:
interface 0/1
no auto-negotiate
addport 1/1
..
interface 0/1
port lacptimeout actor short
port lacptimeout partner short
description 'Bond na XXXXXX slaves'
no spanning-tree port mode
mtu 9216
vlan participation exclude 1
no lacp actor admin state longtimeout
no lacp partner admin state longtimeout
 

Foray

Member
May 22, 2016
59
30
18
Could be because your untagging 113 and not participating in 1(default, untagged).