Guest

Preview Tool

Cisco Bug: CSCvu03675 - FPR2100: ASA console may hang & become unresponsive in low memory conditions

Last Modified

Sep 21, 2020

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases

2.4(1) 9.13(1.10) 9.14(1.6)

Description (partial)

Symptom:
ASA becomes unresponsive. In ASA platform mode, connect asa will hang and user will not be able to connect to ASA. In ASA appliance mode, the console is unresponsive. If in an HA pair, the standby will indicate that it has lost connection with the Active. If connected to the ASA console, you would see "Rebooting... (status 0x9)", but the system will not reboot. From FXOS point-of-view, the app-instance may show an offline state. Traffic through the data ports and ASA management port will cease.

Conditions:
Note: This bug itself is NOT a memory leak. This is a bug that happens when the system runs low on memory, likely due to other conditions (bugs, memory leaks/abnormal memory use, etc.). In order to encounter this bug, you likely will have to have encountered a memory related bug.
A sudden drop in available free memory will trigger an oom_killer event which causes the ASA to be killed. System may not be able to reboot in this case due to helper process hanging after it detects ASA has died. System will then not reboot and be stuck in a hung condition.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.