We had 3 VEM lose connectivity to the VSG, they were working for at least 6 months
Luckily 1 lost contact whilst investigating (log below)
We can see no changes within VMM.
I wiresharked the network
The VEM which have an issue do an ARP broadcast for the VSG the sender IP is 0.0.0.0, nothing is returned by the Cisco 4510
The VEM which are working do an ARP broadcast for the VSG the sender IP is that of the vDATA IP hyperV host- good
I looked into the logs of the vemlog on the Windows Host and can see the following entries, they would tally with the 0.0.0.0 ARPS
The hosts do have an IP address defined within VMM for the vdata connection.
Sep 07 16:05:47.005878 648111 12 1 8 Info [sf_platform_process_pinning_change]: Veth LTL 16 old sgid 0 new sgid 32
Sep 07 16:05:47.005878 648112 12 1 1 Error ProcessPinningUpdateDeferred: Not a virtual port ltl 16
Sep 07 16:05:47.005878 648113 12 1 8 Info [sf_platform_process_pinning_change]: Veth LTL 16 old sgid 32 new sgid 0
Sep 07 16:05:47.005878 648114 12 1 1 Error ProcessPinningUpdateDeferred: Not a virtual port ltl 16
Sep 07 16:06:08.521475 648115 0 99 1 Error sf_report_eid_stats: Could not alloc memory for stats structure. Exiting.
Sep 07 16:06:27.005727 648116 12 1 8 Info [sf_platform_process_pinning_change]: Veth LTL 16 old sgid 0 new sgid 32
Sep 07 16:06:27.005727 648117 12 1 1 Error ProcessPinningUpdateDeferred: Not a virtual port ltl 16
Sep 07 16:06:27.005727 648118 12 1 8 Info [sf_platform_process_pinning_change]: Veth LTL 16 old sgid 32 new sgid 0
Sep 07 16:06:27.005727 648119 12 1 1 Error ProcessPinningUpdateDeferred: Not a virtual port ltl 16
Sep 07 16:06:27.005727 648120 12 1 8 Info [sf_platform_process_pinning_change]: Veth LTL 16 old sgid 0 new sgid 32
Sep 07 16:06:27.005727 648121 12 1 1 Error ProcessPinningUpdateDeferred: Not a virtual port ltl 16
Sep 07 16:06:27.005727 648122 12 1 8 Info [sf_platform_process_pinning_change]: Veth LTL 16 old sgid 32 new sgid 0
Sep 07 16:06:27.005727 648123 12 1 1 Error ProcessPinningUpdateDeferred: Not a virtual port ltl 16
Sep 07 16:08:11.724180 648124 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:08:11.724180 648125 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:08:41.724194 648126 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:08:41.724194 648127 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:09:11.724017 648128 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:09:11.724017 648129 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:09:41.723888 648130 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:09:41.723888 648131 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:10:11.723811 648132 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:10:11.723811 648133 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:10:25.614363 648134 0 99 1 Error VSVC-INFO: heap alloc failed, size 36879
Sep 07 16:10:41.723732 648135 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:10:41.723732 648136 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:11:11.723645 648137 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
Sep 07 16:11:11.723645 648138 0 99 4 Warning sf_query_ip_handler: Cannot get IP for vmknic vPath-CiscoVEM
Sep 07 16:11:41.723529 648139 0 99 4 Warning Error allocating memory needed to call GetAdapterInfo
the VEM are responding on thier IP addresses on the network and can bee seen in the ARP table on the 4510.
