Operational Defect Database
BugZero found this defect 2446 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000g3cDSAQ
Communication lost on FireboxV or XTMv interfaces after you add a new VMware ESXi interface (Fireware v11.x and lower)
Last update date:
9/11/2017
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
If your VMware ESXi configuration includes three or more interfaces, and you add a new ESXi interface, FireboxV or XTMv interfaces in Fireware v11.x or lower might correspond to different ESXi interfaces. This happens because Firebox interfaces correspond to ESXi interfaces based on the order in which ESXi interfaces become active in Fireware v11.x and lower. This can result in lost communication on some or all FireboxV or XTMv interfaces. See Also Communication lost on FireboxV or XTMv interfaces after you upgrade from Fireware v11.x to v.12.0
Workaround/Solution
Before you add a new interface, 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 Addresseth0111:11:11:11:11:11eth1222:22:22:22:22:22eth2333:33:33:33:33:33eth3444:44:44:44:44:44
