"When configuring the traffic storm control level, note the following information:
â¢You can configure traffic storm control on thw port channel interface of an EtherChannel.
â¢Do not configure traffic storm control on ports that are members of an EtherChannel. Configuring traffic storm control on ports that are configured as members of an EtherChannel puts the ports into a suspended state. "
What James is saying is you must apply the the configuration to the Port-Channel interface as with any etherchannel configuration ( with the exception of the description comnmand ).
If you apply config to the physical interface, it will be suspended as the configs are out of sync. When you apply any configuration to the Port-Channel, like trunking an extra vlan, then the config is updated on all members of the channel-group.
I don't understand why the ports are not into âsuspended stateâ, compliance cisco documentation: CISCO - Do not configure traffic storm control on ports that are members of an EtherChannel. Configuring traffic storm control on ports that are configured as members of an EtherChannel puts the ports into a "suspended state".â
How did you configure your storm-control? Did you configure it on the port-channel first? The doc says that if you configure storm control on member ports, it will make the ports suspended because they will have a different port setting configs. Now the result of configuring it on the port-channel, will then result to storm control configurations to be replicated on the member ports automatically.
Did you by any chance configure member ports only for storm control and the result is that the storm control configs got replicated on the port-channel and the ports remained up and in use?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...