Operational Defect Database
BugZero found this defect 3869 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000g3CTSAY
FireCluster fails over unexpectedly when you rename monitored network interfaces
Last update date:
2/16/2023
Affected products:
Firebox M200
Firebox M300
Firebox M270
Firebox M370
Firebox M470
Firebox M570
Firebox M670
Firebox M290
Firebox M390
Firebox M400
Firebox M500
Firebox M440
Affected releases:
All
Fireware
11.x
11.1.x
11.10.x
11.10
11.10.1
11.10.2
11.10.3
11.10.4
11.10.5
11.10.6
Fixed releases:
v12.9.3
Description:
Issue
When you rename a network interface, VLAN interface, or LAG interface that the FireCluster configuration monitors, the health index of the primary cluster member drops, which causes a failover event.
Workaround/Solution
Before you rename the interface, clear the option to monitor the interface link in the FireCluster configuration. Renaming an unmonitored interface does not drop the FireCluster health index or cause a failover event. After you rename the interface, you can re-enable link monitoring in the FireCluster configuration.
