VMware Networking Community
santunezlenovo
Contributor
Contributor

Lost Communication post vMotion

Hello Guys

I have an issue with some vsan nodes.

When vmotion is done from Node1 to Node3 the VMs keep responding and vice versa, but when I Vmotion to node 2 from node3 or node1 the VMs lose all communication. This only happens with node 2.

The 3 nodes are connected to a Cisco 9300L Switch.

I requested the switch configurations and they are not identical with node 2

Node 1 and Node 3 have these configuration on the switches

vMNIC1

  • interface GigabitEthernet2/0/X
  • switchport trunk native vlan 40
  • switchport trunk allowed vlan 40-42
  • switchport mode trunk
  • spanning-tree portfast
  • spanning-tree bpduguard enable

vMNIC3

  • Interface GigabitEthernet1/0/X
  • switchport trunk native vlan 40
  • switchport trunk allowed vlan 40-42
  • switchport mode trunk
  • switchport port-security maximum 5
  • switchport port-security violation restrict
  • switchport port-security
  • storm-control broadcast level bps 2m 1m
  • storm-control multicast level bps 2m 1m
  • spanning-tree portfast
  • spanning-tree bpduguard enable

However, node 2 has these settings on the switch ports

vMNIC1 and vMNIC3 (Is the same configuration on the ports)

  • interface GigabitEthernet2/0/X
  • switchport trunk native vlan 40
  • switchport trunk allowed vlan 40-42
  • switchport mode trunk
  • spanning-tree portfast
  • spanning-tree bpduguard enable

I have not been able to solve the problem, I can only think that it is a matter of configuration of the ports that must be configured identically, remove spanning-tree portfast.

The version of ESXi is 7.0.3 U3f and the vCenter 7.0.3

Thanks for your comments

 

Reply
0 Kudos
1 Reply
Lalegre
Virtuoso
Virtuoso

@santunezlenovo,

This is mostly sure because of the port-security settings, as the MAC Address are advertised and allowed on a single port, when the vMotion happens the traffic is blocked. The good thing is that there is a KB from VMware explaining this: https://kb.vmware.com/s/article/1002811

Take a look with your network team to achieve the changes.

Reply
0 Kudos