FortiGate-200F mgmt port disconnected by storm control after reboot and make it primary
Hi all,
I am running A-P cluster of FortiGate-200F with FortiOS 7.2.10 connected to management network consisting of Juniper EX4400-48T and I am observing:
- when node was in secondary and I will failover to make it primary, everything works as expected
- when node was rebooted, being secondary and I will failover to make it primary, on switch facing MGMT port I do observe twice hit storm control:
Dec 4 11:44:26 EX4400-48T l2ald[38686]: L2ALD_ST_CTL_IN_EFFECT: ge-0/0/19.0: storm control in effect on the port
Dec 4 11:44:26 EX4400-48T l2ald[38686]: L2ALD_ST_CTL_DISABLED: ge-0/0/19.0: storm control disabled port
Dec 4 11:49:17 EX4400-48T l2ald[38686]: L2ALD_STCTL_IF_RECOVERY: ge-0/0/19.0: storm control enabled port. Port recovered on 'Clear ethernet-switching recovery-timeout'
- manual clearing of storm control
Dec 4 11:49:22 EX4400-48T l2ald[38686]: L2ALD_ST_CTL_IN_EFFECT: ge-0/0/19.0: storm control in effect on the port
Dec 4 11:49:22 EX4400-48T l2ald[38686]: L2ALD_ST_CTL_DISABLED: ge-0/0/19.0: storm control disabled port
Dec 4 11:50:09 EX4400-48T l2ald[38686]: L2ALD_STCTL_IF_RECOVERY: ge-0/0/19.0: storm control enabled port. Port recovered on 'Clear ethernet-switching recovery-timeout'
- second storm control manual clean
- everything then works as designed
- no storm control issue on production ports or HA ports
- when reboot is due to FortiOS upgrade, issue with storm control is not observed
Storm control is set to 100M of BUM traffic on 1G physical interface
Unfortunately, it is in production environment, so it is a bit tricky to replicate the issue for TAC engineer.
What exactly should happens on MGMT interface, when node become primary? GARP for sure, but anything else?
What might cause to produce more than 100Mbps of BUM traffic such suddenly?
Thank you for any suggestion.
