I’ve come across instances where new Firepower devices will not register configured interfaces. The issue seems to be related to ESXi 8.0 as it doesn’t support VMXNET interfaces.
The workaround for this issue is to do the following:
- Remove the VMXNET interfaces with the device powered off and replace these with E1000 or E1000e interfaces and save the changes
- Power the device back
- Access the CLI of the Firepower device and reconfigure the management interface
configure network ipv4 manual <IP address> <Subnet Mask> <Gateway>
- Access the Firepower device again using the local device manager or the FMC and verify that the interfaces and the device is reachable. If you’ve not yet configured the interfaces on the device, do so now and then push the configuration changes to the device before verifying the interfaces
After taking these steps, the Firepower device should return to normal behaviour again.
Leave a Reply