Wired Intelligent Edge

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

Did you check the MAC address table?

show mac-address-table vlan 115

Please also check the status of LAG1.

show interface lag 1

Can you also share the physical interface configuration where LAG1 is used?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

Hi, looking at the definition of interface 1/4/1 you posted:

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

there is no trace that that interface is the physical member of (static) logical interface LAG lag1...the latter is an Aggregated Interface (generally made of two or more physical interfaces and running - if dynamic - or not - if static - a Link Aggregation Control Protocol)

Indeed I would have expected to see the VLAN membership set on the lag1 interface and these settings propagates to its physical member interfaces (say your 1/4/1) and, looking at those ones, you should not see any VLAN membership assignments (because those are "in charge" of the lag1 interface only).

This is what we would have expected to eventually see (very basic configurations):

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

and:

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    lag 1

Not to speak that we don't see the other physical member interface that should be involved in forming the (static) logical interface lag1 along with the current 1/4/1.

Please also note that VLAN membership settings which are ruling the Native and the Allowed VLAN Id(s) are the ones (and only these ones) defined into lag1 context so pay attention there.

Side note, you can easily check the VLAN membership of your lag1 interface with this command:

show vlan port lag1

Cheers, Davide.

Assumption: the above set of commands implies that we are speaking about a setup involving an Aruba CX switch (thus running ArubaOS-CX operating system).

Apologies for the confusion, interface 1/4/1 is the switches uplink to the router that passes the 115 network. The lag1 group is interfaces 1/4/2-1/4/5:

interface 1/4/2
    description VM
    no shutdown
    lag 1
interface 1/4/3
    description VM
    no shutdown
    lag 1
interface 1/4/4
    description VM
    no shutdown
    lag 1
interface 1/4/5
    description VM
    no shutdown
    lag 1

Here's the output of show vlan port lag1:

VM_switch# show vlan port lag1

-------------------------------------------------------------------------------
VLAN  Name                            Mode            Mapping
-------------------------------------------------------------------------------
3     VLAN3                           trunk           port
19    VLAN19                          trunk           port
37    VLAN37                          trunk           port
40    VLAN40                          trunk           port
59    VLAN59                          trunk           port
115   VLAN115                         trunk           port
301   VLAN301                         trunk           port
302   VLAN302                         trunk           port

Hi, looking at the definition of interface 1/4/1 you posted:

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

there is no trace that that interface is the physical member of (static) logical interface LAG lag1...the latter is an Aggregated Interface (generally made of two or more physical interfaces and running - if dynamic - or not - if static - a Link Aggregation Control Protocol)

Indeed I would have expected to see the VLAN membership set on the lag1 interface and these settings propagates to its physical member interfaces (say your 1/4/1) and, looking at those ones, you should not see any VLAN membership assignments (because those are "in charge" of the lag1 interface only).

This is what we would have expected to eventually see (very basic configurations):

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

and:

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    lag 1

Not to speak that we don't see the other physical member interface that should be involved in forming the (static) logical interface lag1 along with the current 1/4/1.

Please also note that VLAN membership settings which are ruling the Native and the Allowed VLAN Id(s) are the ones (and only these ones) defined into lag1 context so pay attention there.

Side note, you can easily check the VLAN membership of your lag1 interface with this command:

show vlan port lag1

Cheers, Davide.

Assumption: the above set of commands implies that we are speaking about a setup involving an Aruba CX switch (thus running ArubaOS-CX operating system).

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

The VM folks seem to think everything is correctly configured on their end, this is a screenshot they sent:

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

This is strange. On the switch you have 4 interfaces in LAG1 but on the VM infra side just 2 physical interfaces? Are the interfaces of LAG1 all connect to the same host?

Is the load sharing method in VMware configured correctly? Is it for VLAN115 configured in the same way as for the other VLANs? It should be set to "Route based on IP hash" if I'm correct

The VM folks seem to think everything is correctly configured on their end, this is a screenshot they sent:

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

They are using two MTP to 4 Duplex LC Breakout Cables, two LC connectors from each cable connect to the switch infrastructure and the MTP connects to each of the two ports on the VM side. They've assured me things are configured correctly on their end but I'll reach back out to make sure they haven't missed any configuration steps on their end.

This is strange. On the switch you have 4 interfaces in LAG1 but on the VM infra side just 2 physical interfaces? Are the interfaces of LAG1 all connect to the same host?

Is the load sharing method in VMware configured correctly? Is it for VLAN115 configured in the same way as for the other VLANs? It should be set to "Route based on IP hash" if I'm correct

The VM folks seem to think everything is correctly configured on their end, this is a screenshot they sent:

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

For sure your Switch's lag1 owns a logical interface running at an aggregated speed of 100 Gbps (4 x physical 25 Gbps aggregated as a static LAG - NO LACP is used), are you sure it is the same on the ESXi's vDS side(s)? Maybe you are showing us only a part of the vDS configuration (where are indeed the other two interfaces used by the vSwitch to the physical network)?

They are using two MTP to 4 Duplex LC Breakout Cables, two LC connectors from each cable connect to the switch infrastructure and the MTP connects to each of the two ports on the VM side. They've assured me things are configured correctly on their end but I'll reach back out to make sure they haven't missed any configuration steps on their end.

This is strange. On the switch you have 4 interfaces in LAG1 but on the VM infra side just 2 physical interfaces? Are the interfaces of LAG1 all connect to the same host?

Is the load sharing method in VMware configured correctly? Is it for VLAN115 configured in the same way as for the other VLANs? It should be set to "Route based on IP hash" if I'm correct

The VM folks seem to think everything is correctly configured on their end, this is a screenshot they sent:

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

The VM folks seem to think everything is correctly configured on their end, this is a screenshot they sent:

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

Hi,

I had a similar issue (no control both sides of connexion Servers-Switch(s))... and i want to ask few thinks:

1. A physical and logical diagram is a nice thing that always help me to understand/clarify better in issues like, and sometimes when i ask for it -to the other side of connexion that i dont manage-: magically solve by itself ;-)
2. I saw GIANTs in the interface so i think maybe you have to check "Jumbo" packet.
3. I don´t know that VM tech but defintly could be a factor to check in "2 points of connexion"...
4. I recently have to read (details with Airwave server, D3LL switches, FortyGat UTM, Aruba MM/MDs, etc.) some concepts: LAG, LACP, EtherChannel, Bonding, PortChannel, etc. AND I need to know about what the devices specifically support and some options like (example):  Bonding 2 interfaces yes but what type?? "0,1,2,3,4,5,6" and that is very important because some needs switch configuration other not (like "broadcast" type)... and the "parameters" like in LACP type the dynamic or static and L3 or L4? so: Too much to check for me without control of "both" (host and switch(s)) sides of connexion...

P.D.: Sorry my english, spanish welcome. ;-) please send inbox.

What's the VM infrastructure that the LAG is connecting to?  Have you verified that the VLAN is configured correctly there?

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.

I've got an established lag interface that feeds a VM infrastructure. We're needing to add a new network, vlan 115, to the lag but can't seem to get it to work. The vlan has been established on the switch and it's been added to the uplink:

vlan 115
    description PACS

interface 1/4/1
    description Uplink
    no shutdown
    no routing
    vlan trunk native 317
    vlan trunk allowed 3,16,19,37,59,115,301-302,317,500

It's also been added to the lag interface:

interface lag 1
    description VM LAG
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 3,19,37,40,59,115,301-302

All the other vlans that are currently attached work without issue. I added vlan 115 to a separate interface for testing purposes and the network is working as intended but when using the lag interface connectivity on that network does not work. Any advice on troubleshooting this issue would be appreciated.