<?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: ingress and egress traffic shaping in vSphere™ vNetwork Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271010#M11532</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just to add, Traffic Shaping is applied all the time regardless of available bandwidth.&amp;nbsp; Network I/O Control is prefered traffic shaping. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Apr 2017 10:06:57 GMT</pubDate>
    <dc:creator>vfk</dc:creator>
    <dc:date>2017-04-05T10:06:57Z</dc:date>
    <item>
      <title>ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271006#M11528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all&lt;/P&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are these correct about ingress and egress traffic shaping?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1- ingress = traffic from vm to vds and vds to wan or lan &lt;/P&gt;&lt;P&gt;2- ingress is output traffic&lt;/P&gt;&lt;P&gt;3- egress = traffic from wan or lan to vds and from vds to VM&lt;/P&gt;&lt;P&gt;4- egress is input traffic&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are these correct ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Apr 2017 19:21:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271006#M11528</guid>
      <dc:creator>baber</dc:creator>
      <dc:date>2017-04-04T19:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271007#M11529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some of your points are partially correct&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ingress &amp;amp; egress terms in traffic shapping is from vDS point of view&lt;/P&gt;&lt;P&gt;Ingress = going into or entering vDS&lt;/P&gt;&lt;P&gt;Egress = going outside vDS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See these 2 blog posts&lt;/P&gt;&lt;P&gt;&lt;A href="http://wahlnetwork.com/2013/04/03/leveraging-traffic-shaping-to-control-multi-nic-vmotion-bandwidth/" title="http://wahlnetwork.com/2013/04/03/leveraging-traffic-shaping-to-control-multi-nic-vmotion-bandwidth/"&gt;Leveraging Traffic Shaping to Control Multi-NIC vMotion Bandwidth - Wahl Network&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;IMG alt="ingress-vs-egress-diagram" class="jive-image" height="167" src="http://wahlnetwork.com/wp-content/uploads/2013/03/ingress-vs-egress-diagram.png" style="height: 167px; width: 422.412px;" width="423" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://frankdenneman.nl/2013/01/18/designing-your-vmotion-network-multi-nic-and-netioc/" title="http://frankdenneman.nl/2013/01/18/designing-your-vmotion-network-multi-nic-and-netioc/"&gt;Designing your vMotion network – Multi-NIC vMotion and NetIOC - frankdenneman.nl&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;IMG alt="05-ingress-egress" class="jive-image" height="392" src="http://frankdenneman.nl/wp-content/uploads/2013/01/05-ingress-egress.png" style="width: 469px; height: 391.945px;" width="469" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Apr 2017 19:38:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271007#M11529</guid>
      <dc:creator>bayupw</dc:creator>
      <dc:date>2017-04-04T19:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271008#M11530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Moderator note: Moved to the relevant sub-forum area, VMware vSphere vNetwork.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Apr 2017 19:40:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271008#M11530</guid>
      <dc:creator>bayupw</dc:creator>
      <dc:date>2017-04-04T19:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271009#M11531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you are correct. In VMware-speak:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ingress&lt;/STRONG&gt;: Traffic is going into the vDS from the VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;egress&lt;/STRONG&gt;: Traffic is going out to the VM from the vDS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Within a standard vSwitch, you can only enforce traffic shaping on &lt;STRONG&gt;outbound traffic that is being sent out of an object--such as a VM or VMkernel port--toward another object&lt;/STRONG&gt;. This &lt;STRONG&gt;is referred to by VMware as "ingress traffic" and refers to the fact that data is coming into the vSwitch&lt;/STRONG&gt; by way of the virtual ports. Later, we cover how to set &lt;STRONG&gt;"egress traffic" shaping&lt;/STRONG&gt;, which &lt;STRONG&gt;is the control of traffic being received by a port group headed toward a VM or VMkernel port&lt;/STRONG&gt;, when we start talking about the distributed switch in the next chapter."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Source: Wahl &amp;amp; Pantol. (2014). &lt;EM&gt;Networking for VMware Administrators&lt;/EM&gt;. Palo Alto: VMware Press.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, VMware's definition of this stops at the virtual switch. Per the vSphere 6.5 documentation: "The traffic is classified to ingress and egress according to the traffic direction in the switch, not in the host" (&lt;A href="http://pubs.vmware.com/vsphere-65/index.jsp#com.vmware.vsphere.networking.doc/GUID-964F5A21-0B53-468A-8A05-B71AA91F8A31.html?"&gt;http://pubs.vmware.com/vsphere-65/index.jsp#com.vmware.vsphere.networking.doc/GUID-964F5A21-0B53-468A-8A05-B71AA91F8A31.html?&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Cisco-speak:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ingress&lt;/STRONG&gt;: Traffic moving out of a physical interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;egress&lt;/STRONG&gt;: Traffic moving into a physical interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this means you are also right, because moving past VMware's definition and into Cisco's it's still the same direction. Therefore, ingress is VM &amp;gt; vSwitch &amp;gt; physical switch, and egress is physical switch &amp;gt; vSwitch &amp;gt; VM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Apr 2017 21:25:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271009#M11531</guid>
      <dc:creator>Eric_Allione</dc:creator>
      <dc:date>2017-04-04T21:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271010#M11532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just to add, Traffic Shaping is applied all the time regardless of available bandwidth.&amp;nbsp; Network I/O Control is prefered traffic shaping. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Apr 2017 10:06:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2271010#M11532</guid>
      <dc:creator>vfk</dc:creator>
      <dc:date>2017-04-05T10:06:57Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2979865#M14727</link>
      <description>&lt;P&gt;Do VMware and cisco speak opposite in the topic ?&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jul 2023 12:37:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2979865#M14727</guid>
      <dc:creator>shoeb_khan</dc:creator>
      <dc:date>2023-07-30T12:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2979866#M14728</link>
      <description>&lt;P&gt;Do VMware and Cisco speak opposite in this topic ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jul 2023 12:38:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2979866#M14728</guid>
      <dc:creator>shoeb_khan</dc:creator>
      <dc:date>2023-07-30T12:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: ingress and egress traffic shaping</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2979890#M14729</link>
      <description>What do you mean by “speak opposite”?</description>
      <pubDate>Sun, 30 Jul 2023 19:48:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/ingress-and-egress-traffic-shaping/m-p/2979890#M14729</guid>
      <dc:creator>scott28tt</dc:creator>
      <dc:date>2023-07-30T19:48:18Z</dc:date>
    </item>
  </channel>
</rss>

