<?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: VSP-4000 port clocking up HCInFlowCtrlPkts in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-4000-port-clocking-up-hcinflowctrlpkts/m-p/69352#M861</link>
    <description>&lt;P&gt;It means the device connected to that port is generating Ethernet Flow Control Pause frames.&lt;/P&gt;&lt;P&gt;Which is probably because that device cannot cope with too much traffic, so it tells the switch it is connected to to slow down transmission. Hence the egress buffers on the VSP will allow traffic bursts to that port to be smoothed out. Of course if the egress buffers for that port congest, then the VSP will throw away packets destined for that port, but it will do so in a QoS aware manner. Which is much better than if the device was not generating Flow Control frames, and would be blinded by the bursts of traffic it cannot process anyway. So not necessarily a problem.&lt;/P&gt;</description>
    <pubDate>Thu, 06 Aug 2020 14:50:27 GMT</pubDate>
    <dc:creator>Ludovico_Steven</dc:creator>
    <dc:date>2020-08-06T14:50:27Z</dc:date>
    <item>
      <title>VSP-4000 port clocking up HCInFlowCtrlPkts</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-4000-port-clocking-up-hcinflowctrlpkts/m-p/69351#M860</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;  &lt;P&gt;When graphing an up link port&amp;nbsp;we are seeing HCInFlowCtrlPkts increasing can offer any advice why we are seeing this?&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;The port is not very busy. It’s copper port running at 1Gb.&lt;/P&gt;  &lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="42034fbe01a34a57b57f6718b9679c9d_4bb8d5d8-4442-4ffa-b131-e03e54525be4.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/1956iB3310678E60F53A0/image-size/large?v=v2&amp;amp;px=999" role="button" title="42034fbe01a34a57b57f6718b9679c9d_4bb8d5d8-4442-4ffa-b131-e03e54525be4.png" alt="42034fbe01a34a57b57f6718b9679c9d_4bb8d5d8-4442-4ffa-b131-e03e54525be4.png" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Many thanks&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jul 2020 20:18:31 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-4000-port-clocking-up-hcinflowctrlpkts/m-p/69351#M860</guid>
      <dc:creator>WindyMiller</dc:creator>
      <dc:date>2020-07-21T20:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: VSP-4000 port clocking up HCInFlowCtrlPkts</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-4000-port-clocking-up-hcinflowctrlpkts/m-p/69352#M861</link>
      <description>&lt;P&gt;It means the device connected to that port is generating Ethernet Flow Control Pause frames.&lt;/P&gt;&lt;P&gt;Which is probably because that device cannot cope with too much traffic, so it tells the switch it is connected to to slow down transmission. Hence the egress buffers on the VSP will allow traffic bursts to that port to be smoothed out. Of course if the egress buffers for that port congest, then the VSP will throw away packets destined for that port, but it will do so in a QoS aware manner. Which is much better than if the device was not generating Flow Control frames, and would be blinded by the bursts of traffic it cannot process anyway. So not necessarily a problem.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Aug 2020 14:50:27 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-4000-port-clocking-up-hcinflowctrlpkts/m-p/69352#M861</guid>
      <dc:creator>Ludovico_Steven</dc:creator>
      <dc:date>2020-08-06T14:50:27Z</dc:date>
    </item>
  </channel>
</rss>

