<?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: VMWare ESX 4/DL360 G5/Packet loss on management interface in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213137#M121310</link>
    <description>OK Guys, the solution was simple. The server has been used as a terminal server before we installed ESX. The TS was virtualized and my collegue forgot to tell me that he cloned the MAC address as well. So we had the same MAC address two times in the net. This explains why the VMs, that use unique MAC addresses on their one worked without a problem.&lt;BR /&gt;&lt;BR /&gt;The conflict was resolved and now everything runs smoothly.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dominik</description>
    <pubDate>Wed, 09 Dec 2009 12:19:57 GMT</pubDate>
    <dc:creator>DominikR</dc:creator>
    <dc:date>2009-12-09T12:19:57Z</dc:date>
    <item>
      <title>VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213130#M121303</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I set up today VMWare ESXi 4.0.0 on a DL 360 G5 server. Installation went smooth but when using the vSphere Client I experinced loss of connection to the server from time to time.&lt;BR /&gt;&lt;BR /&gt;I started investigation the issue and detected, that ping to the management IP address have a packet loss of around 13% (see ping plotter screenshot attached).&lt;BR /&gt;&lt;BR /&gt;When using the "Test network" test from VMWare console ping fail too.&lt;BR /&gt;&lt;BR /&gt;On the other hand, Ping to a running VM on the same host run very well and don't experience any loss. Also the link itself is not faulty, the server was used as a terminal server before and worked extremly well.&lt;BR /&gt;&lt;BR /&gt;Has any of you seen this before?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dominik</description>
      <pubDate>Mon, 07 Dec 2009 22:49:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213130#M121303</guid>
      <dc:creator>DominikR</dc:creator>
      <dc:date>2009-12-07T22:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213131#M121304</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;did you check the firewall rules on ESX server ?? &lt;BR /&gt;&lt;BR /&gt;from the SSH/or local console &lt;BR /&gt;&lt;BR /&gt;esxcfg-firewall -q&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Tue, 08 Dec 2009 08:09:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213131#M121304</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2009-12-08T08:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213132#M121305</link>
      <description>Check for duplex mismatch.  If physical switch is configured manually (say 1000/F, 100/F whatever) then ESX needs to be so set as well.&lt;BR /&gt;&lt;BR /&gt;Otherwise everything *must* be set to auto/auto at *both* ends.&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Dec 2009 08:32:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213132#M121305</guid>
      <dc:creator>u84823</dc:creator>
      <dc:date>2009-12-08T08:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213133#M121306</link>
      <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;thank you for your replys.&lt;BR /&gt;&lt;BR /&gt;1. Both the switch port and the NIC have auto negotiation enabled. In addition: If there would be a layer 1 issue, than I think we can savely assume that all network communications would be affected. But only the host traffic has this packet loss rates, not the traffic to the VMs over the same line.&lt;BR /&gt;&lt;BR /&gt;2. I use ESX4i, under /sbin there are several esxcfg-* bins but not an esxcfg-firewall. But unless the ESX firewall has some kind of DoS protection builtin, why would it only drop 20 percent of the packets by random patterns?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dominik</description>
      <pubDate>Tue, 08 Dec 2009 12:55:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213133#M121306</guid>
      <dc:creator>DominikR</dc:creator>
      <dc:date>2009-12-08T12:55:20Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213134#M121307</link>
      <description>Have you tried another workstation ?&lt;BR /&gt;ie: is the link dropping from your workstation the ESXi.</description>
      <pubDate>Wed, 09 Dec 2009 00:39:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213134#M121307</guid>
      <dc:creator>georgemad</dc:creator>
      <dc:date>2009-12-09T00:39:13Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213135#M121308</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;yes I did :-). I tried three different machines as ping source.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dominik</description>
      <pubDate>Wed, 09 Dec 2009 00:53:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213135#M121308</guid>
      <dc:creator>DominikR</dc:creator>
      <dc:date>2009-12-09T00:53:28Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213136#M121309</link>
      <description>A supplemental: When I ping from a VM as source located on the same ESX host, not packet losses occour at the same time when packets are dropped from the outside. That means within the virtual switch - no problem. From an external host to a VM - no problem. Just from a external machine to the ESX host - packets get dropped.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dominik</description>
      <pubDate>Wed, 09 Dec 2009 01:44:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213136#M121309</guid>
      <dc:creator>DominikR</dc:creator>
      <dc:date>2009-12-09T01:44:16Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213137#M121310</link>
      <description>OK Guys, the solution was simple. The server has been used as a terminal server before we installed ESX. The TS was virtualized and my collegue forgot to tell me that he cloned the MAC address as well. So we had the same MAC address two times in the net. This explains why the VMs, that use unique MAC addresses on their one worked without a problem.&lt;BR /&gt;&lt;BR /&gt;The conflict was resolved and now everything runs smoothly.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dominik</description>
      <pubDate>Wed, 09 Dec 2009 12:19:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213137#M121310</guid>
      <dc:creator>DominikR</dc:creator>
      <dc:date>2009-12-09T12:19:57Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare ESX 4/DL360 G5/Packet loss on management interface</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213138#M121311</link>
      <description>Duplicate MAC address issue.</description>
      <pubDate>Wed, 09 Dec 2009 12:20:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/vmware-esx-4-dl360-g5-packet-loss-on-management-interface/m-p/5213138#M121311</guid>
      <dc:creator>DominikR</dc:creator>
      <dc:date>2009-12-09T12:20:31Z</dc:date>
    </item>
  </channel>
</rss>

