Back on the topic of storm-control, I recently deployed some new 3560G
switches and configured them with storm-control. There are some
interesting differences in storm-control on the 3560G and 6500.
The 3560G allowd me to configure storm-control using either bps or pps
rates. I chose to use
On Thu, 2010-09-02 at 16:34 -0400, Jon Lewis wrote:
cloud-uplink-sw-1#sh int count broad
Port BcastSuppDiscards
Gi0/1 0
Gi0/2 0
Gi0/3 0
...
The switch is running the latest code (12.2(55)SE). All the counters are
We just had a incident that a person plugged two ends of a long wire
into two ports of a gig mini switch. The miniswitch then comes to our
access, distribution switch, then comes on layer 2 to our catalyst
6500. That crashed our catalyst 6500 w/ sup720 3bxl, IOS 12.2(33)SXI3.
Now we are reviewing
On (2010-08-26 10:15 -0400), schilling wrote:
Now we are reviewing the whole process, the access switch uplink was
only 73 bits/sec and 8900
packets/sec. This kind of traffic was enough to crash the catalyst 6500.
It shouldn't crash, if you meant there was software forced crash followed
Hi
I just found out I can't set different levels for broadcast and multicast
storm control
I tried this on a C6503-E/Sup32/WS-X6516A running 12.2(33)SXI4a
and a C6506-E/VS-S720-10G/WS-X6724-SFP running 12.2(33)SXI3
Looks like a bug.
-Jens
Thank you everyone. I will set the broadcast and
On Wed, 2010-08-25 at 08:22 +0200, Jens S Andersen wrote:
I just found out I can't set different levels for broadcast and multicast
storm control
Cisco hints at this in the documentation, e.g. for the storm-control
broadcast level command:
Enables broadcast traffic storm control on the
On Wed, 25 Aug 2010, Peter Rathlev wrote:
On Wed, 2010-08-25 at 08:22 +0200, Jens S Andersen wrote:
I just found out I can't set different levels for broadcast and multicast
storm control
Cisco hints at this in the documentation, e.g. for the storm-control
broadcast level command:
Enables
On Wed, Aug 25, 2010 at 10:37 AM, Jon Lewis jle...@lewis.org wrote:
Even clearer than that:
Each port has a single traffic storm control level that is used for all
types of traffic (broadcast, multicast, and unicast).
Traffic storm control monitors the level of each traffic type for which
On Wed, 2010-08-25 at 11:30 -0400, Tim Durack wrote:
Interestingly NX-OS allows a decimal point:
storm-control {broadcast | multicast | unicast} level percentage[.fraction]
So does the 6500 actually. The fraction can be specified with two
decimal digits. :-)
(It'll be many years before I'll
On 24/08/2010, at 8:59 PM, Saku Ytti wrote:
First CSCO box to support policing unknown unicast is EARL7.5 but it is
per chassis instead of per port. I'm not sure if any Cisco can support
per port unknown unicast policing, but if Nexus7k/EARL8 doesn't do it,
I'm betting there isn't any box
On Mon, 2010-08-23 at 13:07 -0400, Christina Klam wrote:
A couple weeks ago, I added storm-control for all of the (two 1-gig
fiber)uplinks to our Cat6500 gateway switch. Because of the large
amounts of drops from the data center switch uplinks, I removed unicast
storm-control. What are your
On (2010-08-24 09:50 +0200), Peter Rathlev wrote:
We use broadcast og multicast storm-control on downlinks towards access
switches, generally at 50% just to make sure a broadcast storm doesn't
spread too much.
I would run 1% broadcast storm control, preferably entered in pps and
rather low
On 24/08/10 09:27, Saku Ytti wrote:
On (2010-08-24 09:50 +0200), Peter Rathlev wrote:
We use broadcast og multicast storm-control on downlinks towards access
switches, generally at 50% just to make sure a broadcast storm doesn't
spread too much.
I would run1% broadcast storm control,
On Tue, 2010-08-24 at 11:27 +0300, Saku Ytti wrote:
But of course you can use 50% too if you have 50% excess capacity to
handle the storm and you know your devices can handle it. In typical
network 1kpps of broadcast is very high number for even 10GE L2,
unless there is some special
On (2010-08-24 11:57 +0200), Peter Rathlev wrote:
Hm... I thought storm-control unicast was exactly for _unknown_
unicast. Otherwise it seems a little retarded (excuse my french).
Blocking/policing unicast as such isn't really helpful, is it?
If it really is just unicast (and not unknown
Thank you everyone. I will set the broadcast and multicast
storm-control to 0.35 (35%) on the interinks between the distribution
and access layer switches. At a later time, I will add the filters to
all edge ports as well.
Thank you for your help,
Christina
Today's Topics:
1. Re:
On (2010-08-24 09:48 -0400), Christina Klam wrote:
Thank you everyone. I will set the broadcast and multicast
storm-control to 0.35 (35%) on the interinks between the distribution
and access layer switches. At a later time, I will add the filters to
all edge ports as well.
0.35 in IOS
All,
A couple weeks ago, I added storm-control for all of the (two 1-gig
fiber)uplinks to our Cat6500 gateway switch. Because of the large
amounts of drops from the data center switch uplinks, I removed unicast
storm-control. What are your thoughts on using storm-control, in
general, on switch
18 matches
Mail list logo
