cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
779
Views
0
Helpful
1
Replies

CSCvk67239 - FTD or ASA traceback and reload in "Thread Name Logger Page fault: Address not mapped"

SwisscomAG
Level 1
Level 1

Hello,

 

Can you please confirm if the 9.6.4.x contains this bug as well. It is stated in the release notes of 9.6.4.20, but the CSCvk67239 does not mention any affected 9.6.x releases whatsoever.

 

Cheers,

Adrian

1 Reply 1

Hi, in the bugtoolkit I cannot find informations about version 9.6. These are the notes related to this bug:

 

Symptom:
ASA Firewalls and Firepower Threat Defense devices may traceback and reload when the state of the unit in a Failover pair or multi-unit cluster changes. For example, when moving from ACTIVE to STANDBY or STANDBY to ACTIVE, or as it joins/leaves a cluster. The problem also occurs during software upgrade.

Conditions:
To encounter the problem, the following conditions must be met:
1) Syslogging to an off-box syslog host must be configured, using the UDP logging protocol
2) FTD devices must be running Firepower 6.2.3.5
ASA devices must be running versions:
9.9.2.16 through 9.9.2.22
9.8.3.9 through 9.8.3.10
Versions outside of these ranges are not affected by the problem.

3) A unit must leave and then join the high availability (cluster or failover) and this might happen during a software upgrade

The problem occurs in cluster and failover high availability setups, and can be triggered during a high-availability upgrade. For example, during the process of upgrading from 6.2.3.5 to a later version such as 6.2.3.6, after one unit successfully upgrades to 6.2.3.6, another unit still running 6.2.3.5 might encounter the problem as it is upgrading and attempting to re-join the cluster.

Workaround:
The problem can be mitigated by disabling UDP syslogging prior to upgrading the software version.

If the device is crashing in a bootloop:
ASA-remove the "logging host" command from startup config.
FTD- contact Cisco TAC to apply the workaround

If you would like to use logging host, Configure TCP logging instead of UDP logging (and consider the 'logging permit-hostdown' command)

If the FTD device is stable following a crash (not continuously crashing) the upgrade will not be running due to the system restart, however could be resumed via CLI using the following command:
#sudo install_update.pl --detach --resume /var/sf/updates/

example (for a 2100 series device):
#sudo install_update.pl --detach --resume /var/sf/updates/Cisco_FTD_SSP_FP2K_Patch-6.2.3.6-37.sh.REL.tar

If there are any issues with the upgrade resume command, or if the device is not stable to run the update, contact TAC.

 

 

Known Affected Releases:
(4)
101.5(1.55)
101.5(1.62)
9.8(3.9)
9.9(2.21)
 
Known Fixed Releases:
(11)
201.3(11.2)
201.3(1.52)
201.1(15.61)
101.5(1.70)
99.3(0.33)
9.10(0.82)
9.9(2.245)
9.9(2.23)
9.8(3.11)
9.8(2.40)
6.2(3.6)