<?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: Burst size, drops before CIR in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/burst-size-drops-before-cir/m-p/20984#M1362</link>
    <description>Hello, normally the CIR is done good. It depends on what kind of traffic generator you are using. If you use an application on windows the application tries to send a constant stream but still windows determines the rate it really egresses out of the NIC and it can be bursty and exceed the CIR.  If you use a dedicated device like IXIA or Spirent the stream is really shaped to the value you configure on the IXIA/Spirent. &lt;BR /&gt;
Could this explain the behavior ?</description>
    <pubDate>Wed, 30 Sep 2015 11:00:00 GMT</pubDate>
    <dc:creator>OscarK</dc:creator>
    <dc:date>2015-09-30T11:00:00Z</dc:date>
    <item>
      <title>Burst size, drops before CIR</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/burst-size-drops-before-cir/m-p/20983#M1361</link>
      <description>Hi everybody&lt;BR /&gt;
&lt;BR /&gt;
We all know improper burst size could result in drops even CIR is not reached. The question is how can we find that optimum burst size which will not cause any drop as CIR approaches on Extreme switch&lt;BR /&gt;
&lt;BR /&gt;
TEST SET UP:&lt;BR /&gt;
&lt;BR /&gt;
Traffic Generator------&amp;gt;p3--Extreme_switch--p2 --Accedian_NID ( LOOPBACK)&lt;BR /&gt;
&lt;BR /&gt;
We are generating 47 MIG stream from the traffic generator.&lt;BR /&gt;
&lt;BR /&gt;
Extreme switch has following configs:&lt;BR /&gt;
&lt;BR /&gt;
Create meter METER_CIR&lt;BR /&gt;
&lt;BR /&gt;
config meter METER_CIR 50000kbs max-burst size 8000kbs&lt;BR /&gt;
&lt;BR /&gt;
Then we apply the meter on ingress on port 3 using ACL.&lt;BR /&gt;
&lt;BR /&gt;
Even though the traffic stream is within CIR, we see drops because of improper burst size.&lt;BR /&gt;
&lt;BR /&gt;
Do we have any formula  on Extreme switch that help us find that optimum burst size ? &lt;BR /&gt;
&lt;BR /&gt;
Much appreciated!!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 29 May 2015 07:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/burst-size-drops-before-cir/m-p/20983#M1361</guid>
      <dc:creator>zeeshan_qadir</dc:creator>
      <dc:date>2015-05-29T07:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Burst size, drops before CIR</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/burst-size-drops-before-cir/m-p/20984#M1362</link>
      <description>Hello, normally the CIR is done good. It depends on what kind of traffic generator you are using. If you use an application on windows the application tries to send a constant stream but still windows determines the rate it really egresses out of the NIC and it can be bursty and exceed the CIR.  If you use a dedicated device like IXIA or Spirent the stream is really shaped to the value you configure on the IXIA/Spirent. &lt;BR /&gt;
Could this explain the behavior ?</description>
      <pubDate>Wed, 30 Sep 2015 11:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/burst-size-drops-before-cir/m-p/20984#M1362</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2015-09-30T11:00:00Z</dc:date>
    </item>
  </channel>
</rss>

