CRC errors on T6 ports after converting from 40GbE to 100GbE

AFF A800, AFF C800, ASA A800, ASA C800 with onboard T6 ports e0a and e0b (T62100-MEZZ) and T62100-CR (P/N X1146A) NIC in Slot 1
AFF A320 onboard T6 ports e0g and e0h (T62100-SABR)
IO Module,2p MC IP,40GbE QSFP+,100GbE QSFP28 (P/N X91146A) - T62100-CR
2p 100GbE iWARP QSFP28 NIC (P/N X1146A) - T62100-CR

After converting T6-based Ethernet ports from 40GbE to 100GbE speeds, a continuous high number of CRC errors are reported due to corrupted Ethernet packets.
Link parameters are not cleared after a 40GbE to 100GbE port conversion, resulting in the generation of malformed packets.
In some cases, the receipt of these corrupted packets can lead to a system disruption (data outage). Examples:
- Vifmgr crashes with NAS protocols disruptions. Examples of ONTAP event messages reported:
  - [node_name: vifmgr: vifmgr.startup.merge.err:error]: The Logical Interface Manager (VIFMgr) encountered errors during startup.
  - vifmgr.startup.failover.err: VIFMgr encountered errors during startup.
  - vifmgr.dbase.checkerror: VIFMgr experienced an error verifying cluster database consistency. Some LIFs might not be hosted properly as a result.
Port speed changes can occur in the following example scenarios. Examples:
- 40GbE Cluster switch or Ethernet data switches are replaced with 100GbE models
- Cluster ports are temporarily configured at 40GbE for a storage system upgrade, but the final port speed configuration is 100GbE
- During a switched to switchless conversion