Symptom
Backup-config.cfg file on primary unit is not written with complete config.
more system:disk0:/backup-config.cfg | in failover - this willl return empty output.
sh run failover on primary :
no failover
backup-config.cfg file in secondary unit has failover config
============
mtu diagnostic 1500
failover
failover lan unit secondary
failover lan interface >
failover replication http
failover link >
failover interface ip > > standby
=========================
Logs on Non-working unit for the file copy request:
Dec 2 04:47:49 firepower SF-IMS[83316]: [83316] LinaConfigTool:LinaConfigTool [INFO] Sent message to Lina: copy /noconfirm startup-config backup-config.cfg
Dec 2 04:47:59 firepower SF-IMS[83316]: [83316] LinaConfigTool:LinaConfigTool [CRITICAL] Timeout waiting to Lina response
==================================
The response is immediate on working unit
Dec 2 04:24:05 firepower SF-IMS[62813]: [62813] LinaConfigTool:LinaConfigTool [INFO] Sent message to Lina: copy /noconfirm startup-config backup-config.cfg
Dec 2 04:24:05 firepower SF-IMS[62813]: [62813] LinaConfigTool:LinaConfigTool [INFO] Received a Lina response.
Conditions
This issue was seen after the FTd upgrade.on checking further we found that backup-config.cfg was not completely written with the running-config ,only patrially written and failover config part was missing from this file.
When the primary ftd copies the backup-config.cfg to startup-config, as the failover config is missing, it ends up in the failover being disabled on primary.
