Description | This article addresses issues with VRRP after upgrading FortiSwitch. |
Scope | FortiSwitch v7.2, v7.4, v7.6. |
Solution |
Issue:
Resolution: Under Engineering Case ID 1085819, an enhancement was implemented to address the VRRP issue observed after a FortiSwitch upgrade.
Enhancement details:
set netmask <netmask>
Condition 1: If netmask is not specified, vrip uses the primary IP netmask of the interface. If vrip and the primary subnet do not match, the configuration is rejected. Condition 2: If netmask is specified, it must match either the primary IP’s netmask or one of the secondary IPs on the interface. If there is no match, the configuration is rejected. Condition 3: During an upgrade, validation is skipped, allowing legacy 'illegal' VRRP configurations to persist. However, such configurations may not function correctly. It is recommended to update the netmask to a valid value.
Config example:
config system interface edit 30 next edit 30 set allowaccess ping https http ssh telnet
Explanation:
Related documentation: VRRP documentation - FortiSwitch administration guide Troubleshooting Tip: Avoiding IP Conflicts Between VRRP Virtual IP and VLAN Interface IP |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.