Operational Defect Database
BugZero found this defect 2445 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000g3bnSAA
Communication lost on FireboxV or XTMv interfaces after you upgrade from Fireware v11.x to v.12.0
Last update date:
11/3/2020
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:
All
Description:
Issue
On a FireboxV or XTMv on a VMWare ESXi server, after you upgrade from Fireware v11.x to v12.0, communication might be lost on one or more interfaces. In Fireware v11.x and lower, Firebox interfaces correspond to ESXi interfaces based on the order in which ESXi interfaces become active. In Fireware v12.x, Firebox interfaces correspond to ESXi interfaces based on the MAC address value of the ESXi interfaces. For example, the lowest ESXi MAC address is assigned to Firebox eth0, and the next lowest MAC address is assigned to eth1. See Also Communication lost on FireboxV or XTMv interfaces after you add a new VMware ESXi interface (Fireware v11.x and lower)
Workaround/Solution
Before you upgrade from Fireware v11.x to v12.0, configure the ESXi MAC addresses in increasing order by the ESXi interface number. This ensures that the Firebox interfaces correspond to the ESXi interfaces as follows: Firebox InterfaceESXi Interface Example ESXi Interface MAC Addresseth0122:22:22:22:22:20eth1222:22:22:22:22:21eth2322:22:22:22:22:22eth3422:22:22:22:22:23
