<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Virtual Switches suddenly stop functioning in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697626#M146607</link>
    <description>&lt;P&gt;Thanks for that.&amp;nbsp; We'll try it and report back.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;</description>
    <pubDate>Wed, 21 Jan 2015 11:53:14 GMT</pubDate>
    <dc:creator>ICS_CS</dc:creator>
    <dc:date>2015-01-21T11:53:14Z</dc:date>
    <item>
      <title>Virtual Switches suddenly stop functioning</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697149#M146594</link>
      <description>&lt;DIV&gt;&lt;P&gt;Several months ago we got a call from a client with a standalone 2012 R2 HyperV host: Absolutely NO network traffic was going through any of the virtual switches, yet we could see no errors or warnings of any kind in any of the logs.&amp;nbsp; Desperate to get them back up and running we simply deleted all the virtual switches, recreated them (identical to what they were) and reattached all the VMs.&amp;nbsp; Note that the port reserved for the host had no issue.&amp;nbsp; At first we chalked it up as a fluke....except that it happened again&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;to a completely different customer&lt;/STRONG&gt;&lt;/EM&gt;.&amp;nbsp; And then third. &amp;nbsp; And then a forth. &amp;nbsp; And then several months after the first incident it happened againt to the first customer.&amp;nbsp;&amp;nbsp; It has become a chronic issue which happens ever few months and no trigger can be found.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only thing common to all of them is A) Server 2012 R2 host and B) HP ProLiant G8 servers (various models, inluding DL360, ML350, and ML310).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All hardware has the latest firmware and drivers as prescribed by HP.&amp;nbsp; All Windows updates are applied in timely fashion.&amp;nbsp; No event, change, or tampering precipitates the event.&amp;nbsp; The virtual switches just stop passing data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've reached out to the Microsoft community on technet but no one there has seen this behavior before.&amp;nbsp;&amp;nbsp; I hope someone here can shed some light on it.&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 20 Jan 2015 17:31:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697149#M146594</guid>
      <dc:creator>ICS_CS</dc:creator>
      <dc:date>2015-01-20T17:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Switches suddenly stop functioning</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697567#M146604</link>
      <description>&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had a quite similar incident, on non-blade proliants : some hyperV VMs juste lose connectivity, with no message whatsoever.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;if it belonged to an hyperV cluster, moving the VM to another node made it resume its network traffic, but putting it back on the first node made the network stop again.&lt;/P&gt;&lt;P&gt;&amp;nbsp; after rebooting the offending node, or disabling an re-enabling the NIC dedicated to the VMs , network would be fine for a few days...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;we placed a support call on Microsoft; &lt;STRONG&gt;turns out there is an issue with VMQ fonctionnality and the Broadcom NetXtreme NIC Driver &lt;/STRONG&gt;(happened to us on gen8 DL360 and ML350):&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A target="_blank" href="http://support.microsoft.com/kb/2986895/en-us"&gt;http://support.microsoft.com/kb/2986895/en-us&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;we disabled VMQ on the node level (no reboot needed, only a short network disruption) and the issue went away !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2015 10:17:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697567#M146604</guid>
      <dc:creator>Arnaud Delaloy</dc:creator>
      <dc:date>2015-01-21T10:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Switches suddenly stop functioning</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697626#M146607</link>
      <description>&lt;P&gt;Thanks for that.&amp;nbsp; We'll try it and report back.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2015 11:53:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/virtual-switches-suddenly-stop-functioning/m-p/6697626#M146607</guid>
      <dc:creator>ICS_CS</dc:creator>
      <dc:date>2015-01-21T11:53:14Z</dc:date>
    </item>
  </channel>
</rss>

