An administrator successfully restores an FMC backup onto a freshly deployed FMC virtual appliance of the exact same software version. However, after the restore completes, all managed FTD devices show a status of 'Offline' or 'Config Apply Failed'. What is the most likely root cause and correct resolution?
Trap 1: The FTD management interface IP addresses must be manually changed…
FTD management IPs are independent of the FMC IP unless routing is broken.
Trap 2: The administrator must run 'configure manager add' on the FMC CLI…
Manager additions are performed on the FTD CLI, not the FMC CLI, and SNMP is unrelated to device registration.
Trap 3: The FTD devices automatically wipe their configurations when an FMC…
FTD devices do not factory reset when an FMC backup is restored; their local policies remain until pushed by FMC.
- A
The FTD management interface IP addresses must be manually changed to match the old FMC management subnet.
Why it fails: FTD management IPs are independent of the FMC IP unless routing is broken.
- B
The administrator must run 'configure manager add' on the FMC CLI to force an SNMP trap listener.
Why it fails: Manager additions are performed on the FTD CLI, not the FMC CLI, and SNMP is unrelated to device registration.
- C
The new FMC has a different system UUID and Internal Certificate Authority keys; the administrator must re-establish trust by re-registering the FTD devices using new registration keys.
FMC trust with managed FTDs relies on its system UUID and Internal Certificate Authority keys, which differ on the freshly deployed appliance. Restoring configuration does not transfer that identity, so devices reject the new manager; re-registering each FTD with new registration keys re-establishes trust.
- D
The FTD devices automatically wipe their configurations when an FMC backup is restored; the administrator must factory reset every FTD.
Why it fails: FTD devices do not factory reset when an FMC backup is restored; their local policies remain until pushed by FMC.