virtual FTD 7.1.0 ESXi incorrect networking mapping

[hmc2500]

I have an issue with FTD not mapping the nics correctly in ESXi. It looks like the Management and diagnostic nics use one virtual nic.  In the FTD console I cannot get the outside and inside nics online. THe status shows disconnected in red. I cannot renumber the nics on the FTD. Is there a way to fix this on the VM? Or am I missing something?

I named the portgroup GNS3 but it is in ESXi. And I've enabled promiscous mode.

[Ruben Cocheno]

@hmc2500 

You need to map your networks specified in the OVF template to networks in your inventory, and then select Next.

Ensure the Management0-0 interface is associated with a VM Network that is reachable from the Internet. Non-management interfaces are configurable from either the management center or from the device manager depending on your management mode.

Table 8. Source to Destination Network Mapping—VMXNET3

Network Adapter	Source Networks	Destination Networks	Function
Network adapter 1	Management0-0	Management0/0	Management
Network adapter 2	Diagnostic0-0	Diagnostic0/0	Diagnostic
Network adapter 3	GigabitEthernet0-0	GigabitEthernet0/0	Outside data
Network adapter 4	GigabitEthernet0-1	GigabitEthernet0/1	Inside data
Network adapter 5	GigabitEthernet0-2	GigabitEthernet0/2	Data traffic (Optional)
Network adapter 6	GigabitEthernet0-3	GigabitEthernet0/3	Data traffic (Optional)
Network adapter 7	GigabitEthernet0-4	GigabitEthernet0/4	Data traffic (Optional)
Network adapter 8	GigabitEthernet0-5	GigabitEthernet0/5	Data traffic (Optional)
Network adapter 9	GigabitEthernet0-6	GigabitEthernet0/6	Data traffic (Optional)
Network adapter 10	GigabitEthernet0-7	GigabitEthernet0/7	Data traffic (Optional)

[Ruben Cocheno]

@hmc2500 

Guide here https://www.cisco.com/c/en/us/td/docs/security/firepower/quick_start/consolidated_ftdv_gsg/ftdv-gsg/m-ftdv-vmware-gsg.html#id_107405

[hmc2500 · Accepted solution]

THanks all. What resolved it was just deploying it without powering on the FTD, then removing all virtual nics and adding them all back before powering it back on. When the nics are added back they will be e1000 nics, not vmnetx3.  That did the trick. 

Found this solution in another post.