topic MLT with LACP: untagged traffic in ExtremeSwitching (VSP/Fabric Engine)

MLT with LACP: untagged traffic

BRMS — Wed, 20 Nov 2019 00:38:11 GMT

we want to connect a server with rhel 7.6 via trunk to our vsp-core-switches. lacp is enabled, mlt and smlt are working. the server uses untagged traffic that should be assigned to an existing vlan at the vsp:

i created an mlt:

mlt 14 enable
interface mlt 14
smlt
lacp enable key 14
exit

and assign this mlt to an interface via the lacp-key:

interface GigabitEthernet 2/2
default-vlan-id 0
auto-negotiate
no shutdown
lacp key 14 aggregation enable timeout-time short
lacp enable
no spanning-tree mstp force-port-state enable
exit

then i created a vlan:

vlan create 139 name "sina_mgmt" type port-mstprstp 0
vlan i-sid 139 10139
interface Vlan 139
ip address 172.28.6.1 255.255.254.0 39
exit

according to:

https://community.extremenetworks.com/extremeswitching-vsp-ers-232923/how-to-define-native-vlan-to-trunk-port-on-voss-vsp-switches-7803786

i can use the following commands to configure the ports accordingly:

interface gigabitethernet 2/2
default-vlan-id 139
untag-port-default-vlan enable

but i get the following errors:

#default-vlan-id 139
Error: port 2/2, Invalid VLAN ID

#untag-port-default-vlan enable
Port 2/2 is part of a MLT
Error: port 2/2, Operation not allowed

can anyone help me configure this or tell me why it doesn’t work as expected?

Re: MLT with LACP: untagged traffic

Jay2009 — Wed, 20 Nov 2019 05:17:33 GMT

Take a look at this.

https://gtacknowledge.extremenetworks.com/pkb_mobile#/articles/en_US/How_To/000034129

Re: MLT with LACP: untagged traffic

Ludovico_Steven — Wed, 20 Nov 2019 21:36:58 GMT

The 1st error is because VLAN 139 has not been added to the port.

First add the VLAN to the port using: vlan members add 139 2/2

Then, if the port has dot1q enabled, you can set VLAN 139 as the PVID (default-VLAN).

The second error I think has to do with a limitation we used to have; we did not allow untag-port-default-vlan on ports which belong to an MLT group. But we changed this in software versions 7.1.3.0 and 8.0.6.0; if you have an earlier software version please upgrade.

Though, looking back to your config, it does not look like you enabled encapsulation-dot1q on the 2/2 port. So your ports are probably untagged. In which case the 2 commands you got errors on are useless, and you should simply use “vlan members add 139 2/2”. Note also that you can add/remove VLANs to the MLT using this command : “[no] mlt <id> vlan <vid-list>” ; this command also works dynamically (no need to have to disable LACP on the port).

Re: MLT with LACP: untagged traffic

BRMS — Thu, 21 Nov 2019 19:00:11 GMT

The newest software version i can find for the VSP8600 is Version 6.3.2.0, which we are using.

dot1q is enabled on the port, i just didn’t post that config snippet.

next try:

sw1:1(config)#vlan members add 139 2/2
sw1:1(config)#interface gigabitEthernet 2/2
sw1:1(config-if)#default-vlan-id 139
sw1:1(config-if)#untag-port-default-vlan enable
Port 2/2 is part of a MLT

Error: port 2/2, Operation not allowed

is this caused by the wrong firmware?

Re: MLT with LACP: untagged traffic

BRMS — Sat, 23 Nov 2019 02:17:56 GMT

got it figured out. i needed to assign the vlan to the interface, then disable lacp on that interface to define the default-vlan-id:

vlan members add 139 2/2
interface gigabitEthernet 2/2
no lacp
default-vlan-id 139
untag-port-default-vlan enable
lacp enable
exit