Loading...
Loading...
ASA reloads when establishing 2 different ASDM sessions from different users or if ASDM logging is enabled. if connected to the ASA console when the traceback is triggered following is displayed: asa# Rebooting... (status 0x8b) No crashinfo is generated but a coredump. This can be identified by checking the coredumpfsys folder on flash (e.g.): asa# dir disk0:/coredumpfsys Directory of disk0:/coredumpfsys/ 139266 -rw- 1485454908 16:37:21 May 03 2019 core.lina.core-0.10466.1556915824.gz <<< Core file created on March 3rd at 4:37pm EST matching the reload event
ASA running any affected code and enabled with ASDM
> Use a single user when establishing ASDM session to the ASA > Use SSH as management method > If a TACACS server is available, configure aaa authentication for http sessions and on the TACACS server allow session only if matching one particular user > For single context mode: Use the command "quota management-session http 1" (This will allow only one single HTTP management session to the box preventing the crash) > For multi context mode: Use the command "quota management-session http 1" on each existing context configured on the box (This will allow only one single HTTP management session to the box preventing the crash) > Disable ASDM logging
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.