Configuring L2 connectivity between VAST Mellanox Switches and Customer Switches

  • Updated on Jan 24, 2026
  • 20 minute(s) read
Prev Next

Terms:

MLAG - Multi-Chassis Link Aggregation (LAG)

IPL - Inter Peer-Link

VPC - Virtual Port Channel

 

When referring to Layer 2 connectivity, the idea is no Layer 3 routing is configured on VAST Ethernet provided switches. The network clients and VAST VIPs may reside on the same L2 network (network subnet & VLAN). If not, the customer should have a router (gateway) which routes between the networks.

In this type of configuration, the VAST Mellanox switches external connectivity is based on one or more MLAG interfaces.  

On the Uplink Switches, the corresponding ports should be aggregated either as regular LAG interfaces or MLAG interface (in case the Uplink switches act as one fabric with MLAG).

Note: different switches vendors may name the MLAG term differently (e.g - Cisco VPC)

During this article, we will refer to two common configurations, apply the relevant changes to your environment based on the guidelines below. 

 

Scenario #1 - Customer Switches part of an MLAG

In scenario #1, an MLAG port channel is configured on both the VAST Mellanox Switches and the customer network switches as can be seen in Figure 1 below. The customer switches are connected through IPL (or the vendor equivalent) connection.

Throughout the scenario examples, we use the following environment:

  1. On each VAST switch, ethernet ports 1/25-1/28 are in use for the switch to switch connectivity

  2. On each Customer switch, ethernet ports 1/1-1/4 are in use for the switch to switch connectivity

  3. The default link speed of 100G is in use

  4. Channel-group (interface-port-channel) number 10 is used

  5. MLAG number 10 is used

  6. VLAN 100 and 101 are in use

  7. The Access VLAN is 1

In your environment, you may use more or fewer ports, different ports, different link speeds, different channel group numbers, different MLAG numbers, and different numbers and amounts of VLANs.

The diagram illustrates a MLAG (Multi Link Aggregation Group) configuration connecting Customer Switch 1 to Customer Switches 2, and similarly connecting Vastt Switch 2 with Vastst Switch 4, utilizing IPL (Inter-Provider Links) as inter-switch connections. This setup ensures redundancy and increased bandwidth by aggregating multiple physical links between switches within each group.

Connectivity diagram - Customer Switches part of an MLAG

VAST Mellanox Switches Configuration

As part of the VAST Cluster installation, the MLAG interface is configured on all the external interfaces on the VAST Mellanox Switches. The external interfaces are the ones connected from VAST Mellanox Switches to the customer switches. The MLAG interface is configured with LACP active mode.

The MTU on all the ethernet and MLAG interfaces are set on 9216 by default, however, the MLAG MTU can be changed to 1500, 9000, or 9214 depending on customer requirements. 

Below is an example of the typical configuration that is generated during cluster installation:

## external port configuration
interface mlag-port-channel 1
interface mlag-port-channel 1 mtu 9216 force
interface ethernet 1/25-1/28 shutdown
interface ethernet 1/25-1/28 mtu 9216 force
interface ethernet 1/25-1/28 speed 100G
interface ethernet 1/25-1/28 no shutdown
interface ethernet 1/25-1/28 mlag-channel-group 1 mode active
interface mlag-port-channel 1 no shutdown

 

VLANs on External Ports

Network packets arrive and leave the VAST Mellanox Switches switches may be tagged or untagged by VLAN. Customers can choose whether VAST will allow tagged packets or not. That is done by configuring the uplinks on VAST Mellanox Switches in one of three modes: access, hybrid, or trunk.

 

Access

Typically, the MLAG interface is configured in access mode which means only untagged traffic will be allowed over the MLAG interfaces.

Example

show interfaces mlag-port-channel 1 switchport
--------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------
Mpo1           access    1

 

Note: in this scenario, the VAST VIP Pools should be set up without VLAN.

In case the communication requires VLAN Tagging (a.k.a IEEE 802.1Q, Dot1q), one of the following should be set on the MLAG port-channel interface:

Trunk

Network packets sent from this port are tagged and the packets received are expected to be tagged. Untagged packets are dropped. Please make sure to add all the required VLANs.

Example

In the example below, VLANs 100 & 101 are allowed on the Trunk MLAG port-channel.

(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write memory
(config) # interface mlag-port-channel 1 switchport mode trunk
(config) # interface mlag-port-channel 1 switchport trunk allowed-vlan 100
(config) # interface mlag-port-channel 1 switchport trunk allowed-vlan add 101

(config) # show interface mlag-port-channel 1 switchport
------------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------------
Mpo1           trunk     N/A              100-101

(config) # write memory

Note: Run the preceding commands on both VAST Mellanox Switches.

Note: In this scenario, the VAST VIP Pools should also be setup with appropriate VLAN tags. For more info refer to https://support.vastdata.com/s/article/UUID-968a7239-fa3f-6c65-3605-0679e257661a

Hybrid

In this mode, both tagged and untagged traffic is allowed as the port expects both tagged and untagged packets. This mode is a combination of Access and Trunk modes. This mode is known in other switches vendors as Trunk + Native VLAN. Please make sure to add all the required VLANs.

Example

In the example below, untagged traffic (VLAN 1), VLANs 100 & 101 are allowed on the Trunk MLAG port-channel.

(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write memory
(config) # interface mlag-port-channel 1 switchport mode hybrid
(config) # interface mlag-port-channel 1 switchport hybrid allowed-vlan 100
(config) # interface mlag-port-channel 1 switchport hybrid allowed-vlan add 101
(config) # show interface mlag-port-channel 1 switchport
--------------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------------
Mpo1           hybrid    1                100-101

(config) # write memory

 

Note: Run the following commands on both VAST Mellanox Switches.  

Note: In this case, VAST VIP Pools with and without VLAN tags will be exposed by the switches to the customer network. You can set VLAN tags were needed as specified in https://support.vastdata.com/s/article/UUID-968a7239-fa3f-6c65-3605-0679e257661a

 

Customer Switches Configuration

The sections below provide guidelines on how to configure the corresponding ethernet ports on the customer switches. In this architecture, a port channel is configured on each of the customer switches. The MLAG port-channel is then configured over the port-channel interfaces.

Arista 

Assuming the Arista switches and VAST Mellanox switches are connected as follows:

The diagram illustrates a redundant network topology utilizing Multi-Layer Aggregation Group (MLAG) and Port Channels to connect Arista Switch 1 with Vast Switch 2, and Arista switch 2 with VAST switch 1, ensuring high availability through interconnected Layer 3 paths labeled as MLAG 10 and IPL.

Arista connectivity diagram - Customer Switches part of an MLAG

The below Switch commands bundle ethernet interfaces 1/1-1/4 in port-channel 10 in LACP active mode, then associate that port-channel with MLAG 10. 

switch# configure terminal
(config)#interface ethernet 1-4
(config-if-et1-6)#channel-group 10 mode active
(config-if-et1-6)#interface port-channel 10
(config-if-po10)#mlag 10
(config-if-po10)#exit
(config)#write

https://www.arista.com/en/um-eos/eos-multi-chassis-link-aggregation#xx1151451

 Note: Please run the preceding commands on both switches.

VLANs configuration

In the case that VLAN tagging is required, please run the following for the relevant VLANs and port-channel interfaces. The Switch commands below set port-channel 10 in Trunk mode and allow VLANs 100 & 101 traffic.

Note: on Arista Switches the VLANs switchport mode is configured on the port-channel interface since no mlag-port-channel-interface exists

switch# configure terminal
(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write
(config) # interface port-channel 10
(config-if-Po10)#switchport mode trunk
(config-if-Po10)#switchport trunk allowed vlan 100
(config-if-Po10)#switchport trunk allowed vlan add 101
(config-if-Po10)#exit
(config)#write

Note: Please run the preceding commands on both Arista switches.

 

In case untagged traffic (Access) is required along with tagged traffic, Arista provides Native Vlan support on top of Trunk switchport mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

switch# configure terminal
(config-if-Po10) switchport trunk native vlan 1
(config-if-Po10) exit
(config)#write


Cisco

Note: the guide below refers to the Cisco Nexus 5000 Series NX-OS Software. Different Cisco switches models may have minor differences. Please contact VAST support for any specific Cisco model inquiries.Assuming the Cisco switches and VAST Mellanox switches are connected as follows:

The diagram illustrates an MLAG setup with Cisco Switch 1 and Vast Switch 2 interconnected via Port Channel 10, forming part of the Virtual Port Channel (VPC) 1 network layer. Additionally, VAST Switch 3 is connected to VAST SWITCH 4 through another MLAG configured as MLAG Port Channel -1, which operates at the same VLAN level as VPC. This configuration ensures redundancy and load balancing across multiple switches within the network topology.

Cisco connectivity diagram - Customer Switches part of an MLAG

The below Switch commands bundle ethernet interfaces 1/1-1/4 in port-channel 10 in LACP active mode, then associate that port-channel with VPC 10.

vpc 10
switch(config)#interface eth1/1-1/4
switch(config-if)channel-group 10
switch(config-if)# interface port-channel 10
switch(config-if)# vpc 10
switch(config-if)# exit
switch(config)# write

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/interfaces/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_chapter_0111.html

Note: Please run the preceding commands on both switches.

VLANs configuration

In the case of VLAN configuration is required, please run the following for the relevant VLANs and port-channel interfaces. The Switch commands below set port-channel 10 in Trunk mode and allow VLANs 100 & 101 traffic.

Note: on Cisco Switches the VLANs switchport mode is configured on the port-channel interface since no mlag-port-channel-interface exists

(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write
(config) # interface port-channel 10
(config-if-Po10)#switchport mode trunk
(config-if-Po10)#switchport trunk allowed vlan 100
(config-if-Po10)#switchport trunk allowed vlan add 101
(config-if-Po10)#exit
(config)#write

 Note: Please run the preceding commands on both Cisco switches.

In case untagged traffic (Access) is required along with tagged traffic, Cisco provides Native Vlan support on top of Trunk switchport mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

(config-if-Po10) switchport trunk native vlan 1
(config-if-Po10) exit
(config)#write

 

 Juniper

Assuming the Juniper switches and VAST Mellanox switches are connected as follows:The below Switch commands bundle ethernet interfaces 0/0/1-0/0/4 in aggregate-ethernet LAG 10 in LACP active mode, then associate that port-channel with MC ae 10.

The diagram illustrates a network configuration with Juniper Switches 1 and Vast Switch 1 connected to Juniper switch 2 and VAST Switch 2 via an Inter-Cluster Link (ICL) and Inter-Pod Link (IPL), respectively, utilizing Multi-Chassis Linked Aggregation Groups (MC-LAG) and MLAG Port Channel 1 for redundancy and load balancing across multiple switches.

Juniper connectivity diagram - Customer Switches part of an MLAG

 

set interfaces ae10 description VAST
set interfaces ae10 aggregated-ether-options minimum-links 1
set interfaces ae10 aggregated-ether-options lacp active
set interfaces et-0/0/1 ether-options 802.3ad ae10
set interfaces et-0/0/2 ether-options 802.3ad ae10
set interfaces et-0/0/3 ether-options 802.3ad ae10
set interfaces et-0/0/4 ether-options 802.3ad ae10
set interfaces ae10 aggregated-ether-options minimum-links 1
set interfaces ae10 aggregated-ether-options lacp system-id 01:02:03:04:01:16
set interfaces ae10 aggregated-ether-options lacp admin-key 16
set interfaces ae10 aggregated-ether-options mc-ae mc-ae-id 10
set interfaces ae10 aggregated-ether-options mc-ae redundancy-group 4
set interfaces ae10 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae10 aggregated-ether-options mc-ae mode active-active
set interfaces ae10 aggregated-ether-options mc-ae status-control standby
set interfaces ae10 aggregated-ether-options mc-ae init-delay-time 240

https://www.juniper.net/documentation/en_US/junos/topics/topic-map/getting-started-mc-lag.html

Note: Please run the preceding commands on both switches. 

VLANs Configuration

In the case of VLAN configuration is required, please run the following for the relevant VLANs and aggregated-ethernet interfaces. The Switch commands below set aggregated-ethernet 10 in Trunk mode and allow VLANs 100 & 101 traffic.

Note: on Juniper Switches the VLANs mode is configured on the aggregate-ethernet interface since no mlag-port-channel-interface exists

set vlans v100 vlan-id 100
set vlans v101 vlan-id 101
set interfaces ae10 unit 0 family ethernet-switching interface-mode trunk
set interfaces ae10 unit 0 family ethernet-switching vlan members v100
set interfaces ae10 unit 0 family ethernet-switching vlan members v101

 

In case untagged traffic (Access) is required along with tagged traffic, Juniper provides Native Vlan support on top of Trunk mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

set interfaces ae10 unit 0 family ethernet-switching native-vlan-id v1

https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/native-vlan-id-edit-interfaces-qfx-series.html

Note: Please run the preceding commands on both Juniper switches.


Dell

Note: the guide below refers to Dell OS 10. Different Dell switches models may have minor differences. Please contact VAST support for any specific Cisco model inquiries.

Assuming the Dell switches and VAST Mellanox switches are connected as follows:

The diagram illustrates a network topology featuring Dell Switches 1 and Dell Switch 2, connected via a virtual link trunking (VLTi) interface, forming an active/active VLT port channel named "Port Channel 10." These switches further connect to MLAG (Multi-Chassis Link Aggregation Group) on both Vast Switch 1 & Vast switch 2 through a dedicated IPL (Inter-Switch Port Channel).

Dell connectivity diagram - Customer Switches part of an MLAG

The below Switch commands bundle ethernet interfaces 1/1/1-1/1/4 in port-channel 10 in LACP active mode, then associate that port-channel with VLT port-channel 10.
 

# configure terminal
OS10(config)# interface port-channel 10
OS10(conf-if-po-10)# vlt-port-channel 10
OS10(conf-if-po-10)# exit
OS10(config)#  interface range ethernet 1/1/1-1/1/4
OS10(conf-range-eth1/1/1-1/1/4)# channel-group 10 mode active
OS10(conf-range-eth1/1/1-1/1/4)# exit
OS10(config)# exit

https://www.dell.com/support/article/en-al/how16532/dell-emc-networking-os10-how-to-set-up-virtual-link-trunking-vlt?lang=en

Note: Please run the preceding commands on both switches.

 

VLANs configuration

In the case of VLAN configuration is required, please run the following for the relevant VLANs and port-channel interfaces. The Switch commands below set port-channel 10 in Trunk mode and allow VLANs 100 & 101 traffic.

Note: on Dell Switches the VLANs switchport mode is configured on the port-channel interface since no mlag-port-channel-interface exists

OS10(config) # vlan 100 name vlan100
OS10(config vlan 100) # exit
OS10(config) # vlan 101 name vlan101
OS10(config vlan 101) # exit
OS10 (config) # interface port-channel 10
OS10(config-if-Po10)# switchport mode trunk
OS10(config-if-Po10)# switchport trunk allowed vlan add 100
OS10(config-if-Po10)# switchport trunk allowed vlan add 101

 

Note: Please run the preceding commands on both Dell switches.

In case untagged traffic (Access) is required along with tagged traffic, Dell provides Access Vlan support on top of Trunk switchport mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

OS10(config-if-Po10) switchport trunk access vlan 1
OS10(config-if-Po10) exit
(config)#write

https://www.dell.com/support/kbdoc/en-us/000137464/dell-emc-networking-os10-how-to-configure-native-access-untagged-vlan-on-a-trunk-port

 

Scenario #2 - Customer Switches are stand-alone

In scenario #2, the customer switches act as stand-alone switches with no MLAG configuration between them. In such a scenario, two MLAG port channels are configured on the VAST Mellanox Switches as can be seen in Figure 6 below. On the customer switches a port channel is configured. 

Note : in this scenario, STP (Spanning Tree Protocol) must be enabled on VAST Mellanox Switches so only half of the links will be actively used.

 

Throughout the scenario examples, we use the following environment:

  1. On each VAST switch, ethernet ports 1/25-1/28 are in use

  2. On each Customer switch, ethernet ports 1/1-1/4 are in use

  3. The default link speed is in use

  4. Channel-group (interface-port-channel) number 10 is used

  5. VLAN 100 and 101 are in use

  6. The Access VLAN is 1

In your environment, you may use more or fewer ports, different ports, different link speeds, different channel group numbers, and different numbers and amounts of VLANs.

The diagram illustrates a network topology featuring Customer Switches 1 and Customer Switch 2 interconnected with Vast Switch 1 (MLAG) and Vastt Switch 3 through LPL and MLAG interfaces, demonstrating redundant connections to ensure high availability in data centers.

Connectivity diagram - Customer Switches are stand-alone

VAST Mellanox Switches Configuration

As part of the VAST Cluster installation in scenario #2, two (or more) MLAG interfaces are configured on the external interfaces of the VAST Mellanox Switches. The external interfaces are the ones connected from VAST Mellanox Switches to the customer switches. The MLAG interfaces are configured with LACP active mode.

The MTU on all the ethernet and MLAG interfaces are set on 9216 by default, however, the MLAG MTU can be changed to 1500, 9000, or 9214 depending on customer requirements.  Below is an example of the typical configuration which is generated during cluster installation:

## enable Spanning Tree Protocol
spanning-tree

## mlag 1 external port configuration
interface mlag-port-channel 1
interface mlag-port-channel 1 mtu 9216 force

interface ethernet 1/25-1/26 shutdown
interface ethernet 1/25-1/26 mtu 9216 force
interface ethernet 1/25-1/26 speed 100G
interface ethernet 1/25-1/26 no shutdown
interface ethernet 1/25-1/26 mlag-channel-group 1 mode active

interface mlag-port-channel 1 no shutdown

## mlag 2 external port configuration
interface mlag-port-channel 2
interface mlag-port-channel 2 mtu 9216 force

interface ethernet 1/27-1/28 shutdown
interface ethernet 1/27-1/28 mtu 9216 force
interface ethernet 1/27-1/28 speed 100G
interface ethernet 1/27-1/28 no shutdown
interface ethernet 1/27-1/28 mlag-channel-group 2 mode active

interface mlag-port-channel 2 no shutdown

 

VLANs on External Ports

Network packets arrive and leave the VAST Mellanox Switches switches may be tagged or untagged by VLAN. Customers can choose whether VAST will allow tagged packets or not. That is done by configuring the uplinks on VAST Mellanox Switches in one of three modes: access, hybrid, or trunk.

Access

Typically, the MLAG interface is configured in access mode which means only untagged traffic will be allowed over the MLAG interfaces.

Example

show interfaces mlag-port-channel 1 switchport
--------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------
Mpo1           access    1

show interfaces mlag-port-channel 2 switchport
--------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------
Mpo2           access    1

Note: in this scenario, the VAST VIP Pools should be setup without VLAN.

In case the communication requires VLAN Tagging (a.k.a IEEE 802.1Q, Dot1q), one of the following should be set on the MLAG port-channel interface:

Trunk

Network packets sent from this port are tagged and the packets received are expected to be tagged. Untagged packets are dropped. Please make sure to add all the required VLANs.

Example

In the example below, VLANs 100 & 101 are allowed on the Trunk MLAG port-channels (Mpo1 and Mpo2)

(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write memory

### MLAG port channel 1 
(config) # interface mlag-port-channel 1 switchport mode trunk
(config) # interface mlag-port-channel 1 switchport trunk allowed-vlan 100
(config) # interface mlag-port-channel 1 switchport trunk allowed-vlan add 101

### MLAG port channel 2 
(config) # interface mlag-port-channel 2 switchport mode trunk
(config) # interface mlag-port-channel 2 switchport trunk allowed-vlan 100
(config) # interface mlag-port-channel 2 switchport trunk allowed-vlan add 101

(config) # show interface mlag-port-channel 1 switchport
------------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------------
Mpo1           trunk     N/A              100-101


(config) # show interface mlag-port-channel 2 switchport
------------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------------
Mpo2           trunk     N/A              100-101

(config) # write memory

Note: Run the preceding commands on both VAST Mellanox Switches.

Note: In this scenario, the VAST VIP Pools should also be setup with appropriate VLAN tags. For more info refer to https://support.vastdata.com/s/article/UUID-968a7239-fa3f-6c65-3605-0679e257661a


Hybrid

In this mode, both tagged and untagged traffic are allowed as the port expects both tagged and untagged packets. This mode is a combination of Access and Trunk modes. This mode is known in other switches vendors as Trunk + Native VLAN. Please make sure to add all the required VLANs.

Example

In the example below, untagged traffic (VLAN 1), VLANs 100 & 101 are allowed on the Trunk MLAG port-channel.

(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write memory

### MLAG port channel 1 
(config) # interface mlag-port-channel 1 switchport mode hybrid
(config) # interface mlag-port-channel 1 switchport hybrid allowed-vlan 100
(config) # interface mlag-port-channel 1 switchport hybrid allowed-vlan add 101

### MLAG port channel 2 
(config) # interface mlag-port-channel 2 switchport mode hybrid
(config) # interface mlag-port-channel 2 switchport hybrid allowed-vlan 100
(config) # interface mlag-port-channel 2 switchport hybrid allowed-vlan add 101
(config) # show interface mlag-port-channel 1 switchport
--------------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------------
Mpo1           hybrid    1                100-101

(config) # show interface mlag-port-channel 2 switchport
--------------------------------------------------------------------------
Interface      Mode      Access vlan      Allowed vlans
--------------------------------------------------------------------------
Mpo2           hybrid    1                100-101

(config) # write memory

 

Note: Run the following commands on both VAST Mellanox Switches.  

Note: In this scenario, in case tagged traffic is required, the VAST VIP Pools should also be set up with appropriate VLAN tags.
For more info refer to https://support.vastdata.com/s/article/UUID-968a7239-fa3f-6c65-3605-0679e257661a  

Customer Switches Configuration

The sections below provide guidelines on how to configure the corresponding ethernet ports on the customer switches. In this architecture, a port channel is configured on each of the stand-alone customer switches. 

 

Arista

Assuming the configuration in Figure 6, the commands below assign Ethernet interfaces 1/1-1/4 to channel-group 10 (creating the channel group if it does not already exist), enable LACP on those interfaces, and place the channel group in a negotiating state.

switch# configure terminal
switch(config)#interface ethernet 1-4
switch(config-if-Et1-6)#channel-group 10 mode active
switch(config-if-Et1-6)#exit
switch(config)# write

https://www.arista.com/en/um-eos/eos-port-channels-and-lacp

Note: Please run the preceding commands on both Arista switches.

 

VLANs Configuration

In the case that VLAN configuration is required, please run the following for the relevant VLANs and port-channel interfaces. The Switch commands below set port-channel 10 in Trunk mode and allow VLANs 100 & 101 traffic.

switch# configure terminal
(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write
(config) # interface port-channel 10
(config-if-Po10)#switchport mode trunk
(config-if-Po10)#switchport trunk allowed vlan 100
(config-if-Po10)#switchport trunk allowed vlan add 101
(config-if-Po10)#exit
(config)#write

Note: Please run the preceding commands on both Arista switches. 

In case untagged traffic (Access) is required along with tagged traffic, Arista provides Native Vlan support on top of Trunk switchport mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

switch# configure terminal
(config-if-Po10) switchport trunk native vlan 1
(config-if-Po10) exit
(config)#write

https://www.arista.com/en/um-eos/eos-port-channels-and-lacp

Note: Please run the preceding commands on both Arista switches.

Cisco

Note: the guide below refers to Cisco Nexus 5000 Series NX-OS Software. Different Cisco switches models may have minor differences. Please contact VAST support for any specific Cisco model inquiries.

Assuming the configuration in Figure 6, the commands below assign Ethernet interfaces 1/1-1/4 to channel-group 10 (creating the channel group if it does not already exist), enable LACP on those interfaces, and place the channel group in a negotiating state.

switch# configure terminal
switch (config)# interface ethernet 1/1-1/4
switch(config-if)# channel-group 10 mode active
switch(config-if)# exit
switch (config)# write

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/interfaces/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_chapter_0110.html

Note: Please run the preceding commands on both Cisco switches.

VLANs Configuration

In the case of VLAN configuration is required, please run the following for the relevant VLANs and port-channel interfaces. The Switch commands below set port-channel 10 in Trunk mode and allow VLANs 100 & 101 traffic.

(config) # vlan 100 name vlan100
(config vlan 100) # exit
(config) # vlan 101 name vlan101
(config vlan 101) # exit
(config) # write
(config) # interface port-channel 10
(config-if-Po10)#switchport mode trunk
(config-if-Po10)#switchport trunk allowed vlan 100
(config-if-Po10)#switchport trunk allowed vlan add 101
(config-if-Po10)#exit
(config)#write

 

In case untagged traffic (Access) is required along with tagged traffic, Cisco provides Native Vlan support on top of Trunk switchport mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

(config-if-Po10) switchport trunk native vlan 1
(config-if-Po10) exit
(config)#write

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/VLANs.html

Note: Please run the preceding commands on both Cisco switches.

 

Juniper

Assuming the configuration in Figure 6, the commands below assign Ethernet interfaces 0/0/1-0/0/4 to aggregated ethernet LAG 10, enable LACP on those interfaces, and place the aggregated-ethernet interface in a negotiating state.

set interfaces ae10 description VAST
set interfaces ae10 aggregated-ether-options minimum-links 1
set interfaces ae10 aggregated-ether-options lacp active
set interfaces et-0/0/1 ether-options 802.3ad ae10
set interfaces et-0/0/2 ether-options 802.3ad ae10
set interfaces et-0/0/3 ether-options 802.3ad ae10
set interfaces et-0/0/4 ether-options 802.3ad ae10

 

https://www.juniper.net/documentation/en_US/junos/topics/example/chassis-cluster-lag-lacp-configuring-cli.html

Note: Please run the preceding commands on both switches.


VLANs Configuration

In the case of VLAN configuration is required, please run the following for the relevant VLANs and aggregated-ethernet interfaces. The Switch commands below set aggregated-ethernet 10 in Trunk mode and allow VLANs 100 & 101 traffic.

Note: on Juniper Switches the VLANs mode is configured on the aggregate-ethernet interface since no mlag-port-channel-interface exists

set vlans v100 vlan-id 100
set vlans v101 vlan-id 101
set interfaces ae10 unit 0 family ethernet-switching interface-mode trunk
set interfaces ae10 unit 0 family ethernet-switching vlan members v100
set interfaces ae10 unit 0 family ethernet-switching vlan members v101

 

In case untagged traffic (Access) is required along with tagged traffic, Juniper provides Native Vlan support on top of Trunk mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

set interfaces ae10 unit 0 family ethernet-switching native-vlan-id v1

https://kb.juniper.net/InfoCenter/index?page=content&id=KB11013&cat=QFX_SERIES&actp=LIST

Note: Please run the preceding commands on both Juniper switches.

 

Dell

Note: the guide below refers to Dell OS 10. Different Dell switches models may have minor differences. Please contact VAST support for any specific Dell model inquiries.

Assuming the configuration in Figure 6, the commands below assign Ethernet interfaces 1/1/1-1/1/4 to channel-group 10 (creating the channel group if it does not already exist), enable LACP on those interfaces, and place the channel group in a negotiating state.

# configure terminal 
OS10(config)# interface port-channel 10
OS10(conf-if-po-10)# exit
OS10(config)#  interface range ethernet 1/1/1-1/1/4
OS10(conf-range-eth1/1/1-1/1/4)# channel-group 10 mode active
OS10(conf-range-eth1/1/1-1/1/4)# exit
OS10(config)# exit
OS10(config)#write

https://www.dell.com/support/kbdoc/en-il/000121857/how-to-create-link-aggregation-groups-lags-on-dell-networking-powerconnect-switches

Note: Please run the preceding commands on both Dell switches.

VLANs Configuration

In the case of VLAN configuration is required, please run the following for the relevant VLANs and port-channel interfaces. The Switch commands below set port-channel 10 in Trunk mode and allow VLANs 100 & 101 traffic.

OS10(config) # vlan 100 name vlan100
OS10(config vlan 100) # exit
OS10(config) # vlan 101 name vlan101
OS10(config vlan 101) # exit
OS10 (config) # interface port-channel 10
OS10(config-if-Po10)# switchport mode trunk
OS10(config-if-Po10)# switchport trunk allowed vlan add 100
OS10(config-if-Po10)# switchport trunk allowed vlan add 101

 

In case untagged traffic (Access) is required along with tagged traffic, Dell provides Access Vlan support on top of Trunk switchport mode. This is known as Hybrid mode in other switches vendors.
Please run the commands to configure in case such configuration is required.

The access (untagged) VLAN in this example is set to 1.

OS10(config-if-Po10) switchport trunk access vlan 1
OS10(config-if-Po10) exit
(config)#write

https://www.dell.com/support/kbdoc/en-us/000137464/dell-emc-networking-os10-how-to-configure-native-access-untagged-vlan-on-a-trunk-port

Note: Please run the preceding commands on both Dell switches.

Related articles