View Only


This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.

  • 1.  storm-control

    Posted 09-28-2012 02:20

    show ethernet-switching-options    
    storm-control {
        interface all {
            bandwidth 1000;


    this will control the input rate for each interface is 1000kbps,right?

    not for the output?


  • 2.  RE: storm-control

    Posted 09-28-2012 02:34
    Correct. Storm-control works only for the ingress traffic.


  • 3.  RE: storm-control

    Posted 09-28-2012 02:38
    whether 100kbs is sufficent in network for broadcast/unknown unicast /multicast(there should be no mc in our network)

  • 4.  RE: storm-control
    Best Answer

    Posted 09-28-2012 02:44
    That depends on your traffic nature/patterns, really.
    I would suggest using wireshark and let it run for a couple of work-days. You can then make graphs on wireshark and check out the average/maximum traffic load for the ports; and then configure appropriate values.

  • 5.  RE: storm-control

    Posted 09-28-2012 02:49
    I missed one question how to check many storm exceeds the configured lmit,how to check the counter?

  • 6.  RE: storm-control

    Posted 09-28-2012 02:58
    To check the traffic ingressing the interface, you can use "show interfaces <int> extensive" command. It shows the ingress/egress rates for the interface.

    To check if a port has been error-disabled by storm-control, you can use "show ethernet-switching interfaces" command.

    In case you haven't configured the storm-control action to disable the port, then a syslog message should be generated reflecting that storm-control has started kicking in on the interface.