<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - traffic monitor between VM guests within the same ESX host</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esx3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Sat, 15 Nov 2008 07:46:31 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-11-15T07:46:31Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: traffic monitor between VM guests within the same ESX host</title>
      <link>http://communities.vmware.com/message/1099851?tstart=0#1099851</link>
      <description>Depending upon the organization, even enabling promiscuous mode might require change management.&lt;br /&gt;
&lt;br /&gt;
Another idea, assuming your switch is capable, you can bind that machine to it's own vSwitch and physical Nic, mirror the port it's plugged into (at the physical switch level) and put a sniffer on whatever is plugged into the mirrored port.  If change management is a big issue in your organization, this one might be harder as it requires changes to the virtual side and the physical switch.</description>
      <pubDate>Sat, 15 Nov 2008 07:46:31 GMT</pubDate>
      <author>twoodland</author>
      <guid>http://communities.vmware.com/message/1099851?tstart=0#1099851</guid>
      <dc:date>2008-11-15T07:46:31Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: traffic monitor between VM guests within the same ESX host</title>
      <link>http://communities.vmware.com/message/1099850?tstart=0#1099850</link>
      <description>Yup, may not need promiscuous if you're doing the "sniffing" from one of the VMs you want to monitor. Generally I don't like installing sniffer software in one of the VMs I want to monitor to avoid a configuration change to the VM and a configuration change typically requires a change request in most organizations. Agreed that this should only be an "on when you need it, then turn it back off" kind of thing...</description>
      <pubDate>Sat, 15 Nov 2008 07:38:13 GMT</pubDate>
      <author>Craig Baltzer</author>
      <guid>http://communities.vmware.com/message/1099850?tstart=0#1099850</guid>
      <dc:date>2008-11-15T07:38:13Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: traffic monitor between VM guests within the same ESX host</title>
      <link>http://communities.vmware.com/message/1099833?tstart=0#1099833</link>
      <description>I don't think you will need to enable promiscuous mode (unless you care about dropped packets as well).  If you use a network monitor one of on the hosts you want to monitor, that should be all that is required.  You need to be careful when you enable promiscuous mode, it can be hard on cpu resources if you have a ton of traffic.</description>
      <pubDate>Sat, 15 Nov 2008 07:30:30 GMT</pubDate>
      <author>twoodland</author>
      <guid>http://communities.vmware.com/message/1099833?tstart=0#1099833</guid>
      <dc:date>2008-11-15T07:30:30Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: traffic monitor between VM guests within the same ESX host</title>
      <link>http://communities.vmware.com/message/1099847?tstart=0#1099847</link>
      <description>&lt;br /&gt;
Sure. Sniffer-type apps (i.e. Windows Network Monitor, tcpdump, wireshark, etc.) can be installed in a VM, and then enable promiscuous mode on the vSwitch and VM Network port group that connects the VMs. You can also use tcpdump from the service console (&lt;a class="jive-link-external" href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;#38;cmd=displayKC&amp;#38;externalId=1000880"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;#38;cmd=displayKC&amp;#38;externalId=1000880&lt;/a&gt; has some info on how to set it up)...&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 15 Nov 2008 07:19:15 GMT</pubDate>
      <author>Craig Baltzer</author>
      <guid>http://communities.vmware.com/message/1099847?tstart=0#1099847</guid>
      <dc:date>2008-11-15T07:19:15Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>traffic monitor between VM guests within the same ESX host</title>
      <link>http://communities.vmware.com/message/1099843?tstart=0#1099843</link>
      <description>&lt;br /&gt;
If I have 2 VM guests that are reside on the same esx hosts, can you still use a sniffer to monitor the network traffic between them?&lt;br /&gt;
&lt;p /&gt;
dwc</description>
      <pubDate>Sat, 15 Nov 2008 06:45:43 GMT</pubDate>
      <author>dwchan</author>
      <guid>http://communities.vmware.com/message/1099843?tstart=0#1099843</guid>
      <dc:date>2008-11-15T06:45:43Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
  </channel>
</rss>

