Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Sensitive customer and possible database corruption.
FTD unit with Secondary/Active role became unresponsive and turned to a start-failed status in the Firepower Chassis Manager. Fault error log: XXX /ssa # sho fault Severity Code Last Transition Time ID Description Major F1551 2021-09-17T11:25:40.984 262730 Failed to start App Instance ftd on slot 1. Error: STOP_FAILED CSP_Stop_App_Error XXX@tex opt-cisco-platform-logs]$ cat messages | grep -i failed 1065292 Sep 17 10:35:05 NLACOIGW-SECNEC412/2 CSPM: ERROR: APP STOP failed for cisco-ftd.6.2.0.363__ftd_001_JAD20500640SKV3KC6 autorun; Pls check corresponding app logs 1065293 Sep 17 10:35:05 NLACOIGW-SECNEC412/2 SSP-RM: ERROR: ServiceStop Timeout and Failed 1065297 Sep 17 10:35:07 NLACOIGW-SECNEC412/2 SMA: ERROR ExecProcessorTemp [139832315602688]: platform script returned failure exit code [105] for command [stop], appId [ftd_001_JAD20500640SKV3KC6], errMsg[STOP_FAILED CSP_Stop_App_Error] failed STOP_FAILED CSP_Stop_App_Error 1065315 Sep 17 11:55:44 NLACOIGW-SECNEC412/2 CSPM: ERROR: APP STOP failed for cisco-ftd.6.2.0.363__ftd_001_JAD20500640SKV3KC6 autorun; Pls check corresponding app logs 1065316 Sep 17 11:55:44 NLACOIGW-SECNEC412/2 SSP-RM: ERROR: ServiceStop Timeout and Failed 1065320 Sep 17 11:55:45 NLACOIGW-SECNEC412/2 SMA: ERROR ExecProcessorTemp [139832315602688]: platform script returned failure exit code [105] for command [stop], appId [ftd_001_JAD20500640SKV3KC6], errMsg[STOP_FAILED CSP_Stop_App_Error] failed STOP_FAILED CSP_Stop_App_Error 93 Sep 17 16:54:25 NLACOIGW-SECNEC412/2 ssp_vnic[12280]: [Tue Sep 17 04:36:44 UTC 2019] BIND> ERR: failed to bind VNIC 10 [DRVNAME:vfio-pci PCISLOT:0000:0f:00.0] 195 Sep 17 16:54:25 NLACOIGW-SECNEC412/2 ssp_vnic[12280]: [Fri Sep 17 16:53:48 UTC 2021] BIND> ERR: failed to bind VNIC 10 [DRVNAME:vfio-pci PCISLOT:0000:0f:00.0] 298 Sep 17 16:55:11 NLACOIGW-SECNEC412/2 SSP-RM: ERROR: VnicRequest: Failed to update Runtime VNIC RMDB-Bind/unbind request. 299 Sep 17 16:55:11 NLACOIGW-SECNEC412/2 SSP-RM: ERROR: VnicRequest: Failed to update Runtime VNIC RMDB-Bind/unbind request. "show fault severity major detail" Fault Instance Severity: Major Code: F1551 Last Transition Time: 2021-09-17T11:25:40.984 ID: 262730 Status: None Description: Failed to start App Instance ftd on slot 1. Error: STOP_FAILED CSP_Stop_App_Error <------ Affected Object: sec-svc/slot-1/app-inst-ftd Name: Sm App Instance App Start Failed Cause: Appinstance Start Failed Type: Server Acknowledged: No Occurrences: 2 <------------------- Creation Time: 2021-09-17T10:35:07.593 <------------------- Original Severity: Major Previous Severity: Cleared Highest Severity: Major Reset Reason for this card: Image Version: 5.0(3)N2(4.31) Reset Reason (LCM): Unknown (0) at time Tue Nov 9 15:19:21 2021 Reset Reason (SW): Reset Requested by CLI command reload (9) at time Fri Sep 17 16:24:29 2021 <----- Reboot time Service (Additional Info): Reset Reason (HW): Unknown at time Fri Sep 17 16:24:29 2021 XXX(fxos)# show system reset-reason ----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) --- 1) At 6503 usecs after Fri Sep 17 16:24:35 2021------------------------CLI Reload due to the incident. Reason: Reset Requested by CLI command reload Service: Version: 5.0(3)N2(4.31)
----------------------------------------------- Affected Device and software code: ----------------------------------------------- FP4120 - FXOS 2.3.1.112 with FTD 6.2.3 in HA configuration mode. -The customer did a manual failover and rebooted the secondary unit but the "Start-failed" state persists. After reloading the secondary module, the module has been recovered and became accessible but the chassis manager still showed as start-failed. -No FXOS, snort core files were found nor lina crashes.
Re-enable the app instance (as per BEMS01351219)
BEMS:BEMS01351219 https://clpsvs.cloudapps.cisco.com/services/clip/main/app/service/bems/engagement/736008989/engagement