Troubleshooting Tip: How to verify working of storm-control
| Description | This article describes how to verify working of storm-control. |
| Scope | All FortiSwitch versions. Keywords: packet drop, storm-control. |
| Solution | Related links: https://docs.fortinet.com/document/fortiswitch/7.0.1/administration-guide/13233/storm-control
To verify the storm-control: For Traffic generator, use Third-party applications. eg. Cola-soft. For Traffic capture, port-mirror capture on the FortiSwitch as mentioned on the below link: https://community.fortinet.com/t5/FortiSwitch/Technical-Tip-SPAN-Port-Mirroring/ta-p/189430
2) Port1 and Port2 should be configured in same VLAN.
3) Enable storm-control globally (or per port strom-control) with 100 packet/sec with Broadcast, multicast and unknown unicast.
To configure Storm-control globally for managed FortiSwitches:
# config switch-controller storm-control set rate <rate> set unknown-unicast {enable | disable} set unknown-multicast {enable | disable} set broadcast {enable | disable} end
To configure Storm-control port based on the Managed FortiSwitches:
# config switch-controller storm-control-policy edit <storm_control_policy_name> set description <description_of_the_storm_control_policy> set storm-control-mode override set rate <1-10000000 or 0 to drop all packets> set unknown-unicast {enable | disable} set unknown-multicast {enable | disable} set broadcast {enable | disable} next end
# config switch-controller managed-switch edit <FortiSwitch_serial_number> config ports edit port5 set storm-control-policy <storm_control_policy_name> next end
4)Send broadcast (any packets with destination mac ffff.ffff.ffff) at 200 packet/sec to port1; then verify port2 receives broadcast packets at 100 packet/sec.
Note. Traffic generation and capture has to be done as mentioned on 1).
Disable debug after verifying the logs.
FSW# diagnose switch physical-ports hw-counter remove rx 4 PDISC port2
Storm-control is implemented in hardware, so there are no logs to indicate traffic dropped by storm-control. Packet size could impact storm-control too.
Besides the rate limit of packet per second configuration, the burst-size-level configuration deals with burst packets in storm-control.
So, the different traffic patterns (rate, packet size, burst) will impact the drop decision of storm-control in ASIC hardware. |
