Quantcast
Channel: VMware Communities: Message List - VMware ESXi 5
Viewing all articles
Browse latest Browse all 61617

Re: Cluster Networking Issues

$
0
0

Hi all - great to see some activity on this post as the issue from our point of view is still very much unresolved.

Without tempting fate we've not had a re-occurance since the last outage which has to be around 6 months ago.

We have also just been assigned a new account manager by HP and have asked for the case we logged to be reviewed again. As things stand HP had exhausted troubleshooting from their end. All we have is a set of formal procedures to capture as much information as possible if this re-occurs (logs, wireshark captures, etc).

 

Reading through your indivdual situations, ours sounds similar in terms of the net result, but differs in that I do not remember seeing any errors recorded in VCs logs, or any issues with it's domain state. I don't ever remember a NO_COMM error as I'm sure the domain was still accessible. VC thought everything was operating normally... As things stood we were in such a blind panic to restore services, apart from log gathering, my memory of the event is hazy! We simply powered down and up the entire chassis and everything carried on as normal. I then remember having some weird vNIC errors on around 50% of VMs where they failed to power on. We had to remove the affected vNICs. re-add them and the VM powered up. VMware couldn't explain this vNIC fault as we logged a case after we had recovered services.

 

In response to queries, we have 'Link status only' set in our vDS. I also can't see any pause frame errors -

Dot3InPauseFrames: 0
Dot3OutPauseFrames: 0

 

Just looking through hostd now and from the logs back when we had the failure and I can't see anything related to NetQ. I can post the hostd log from the time of the failure if thats of any use?

 

Thanks in advance!


Viewing all articles
Browse latest Browse all 61617

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>