At my work place we have our Exchange 2010 running completely on VMware. We use SCOM as our main monitoring tool so we purchased Veeam nWorks to pass on all the metrics to SCOM and generate alerts where needed.
Over the pass few weeks we started to receive alerts regarding dropped packets from an host. At first we thought we had over subscribed the bandwidth but after looking at performance charts within vCenter for the host. We noticed that we had been having drop packets for a while but was unaware of the issues as it never hit the threshold for SCOM to send an alert for us. After seeing this we quickly checked across all our host in case we had an underlying issue waiting to happen and found out is was only happening on host which was hosting exchange. Further investigation we discovered it was coming from just our mailbox servers.
There was an article released from VMware regarding this problem. The issue is due to the fact we are using vmxnet3 network cards and when Exchange has a burst of traffic the network card buffers can't take it. The workaround or fix is to increase buffer on the network card. The process is described in the KB article:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2039495
Subscribe to:
Post Comments (Atom)
Azure Resource Support for Availability Zone
Over the years, an increasing number of services are consumed in the cloud and as architects one of the key considerations is designing the ...
-
For Windows virtual machines deployed into Azure using marketplace images you may have created rules in your NSG or firewalls to allow the s...
-
There is an article by Microsoft that lists all the URLs that Visual Studio requires to install or interaction with Azure services if you wa...
-
If you have Azure AD Premium P2 licences one of the reasons would of been to use Privileged Identity Management (PIM) as its a great tool to...
No comments:
Post a Comment