<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ASA boot/console logs to file in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345231#M1123415</link>
    <description>&lt;P&gt;I'm planning to update the ASA and ROMMON software on a ISA3000. I've tested it in our lab first and during the testing I've been connected through the console port. This is nice as I can see what is going on during the reload processes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, when I'll perform the upgrade on the target system, I'll only have an SSH connection, no console. Is there a way to get the same messages that can be seen during a reboot with an active console session written to a file? Or how can I get the same info, either live, or downloaded afterwards, from an SSH session?&lt;/P&gt;&lt;P&gt;I've tried to enable syslogging to file, but I can't find any of the messages I'm interested in there. I wondering if the messages I'm interested in do not come from the syslog service?&lt;/P&gt;&lt;P&gt;These are the current log settings:&lt;/P&gt;&lt;PRE&gt;FW01/sec/NoFailover# show logg&lt;BR /&gt;Syslog logging: enabled&lt;BR /&gt;Facility: 20&lt;BR /&gt;Timestamp logging: enabled&lt;BR /&gt;Timezone: enabled&lt;BR /&gt;Logging Format: disabled&lt;BR /&gt;Hide Username logging: enabled&lt;BR /&gt;Standby logging: disabled&lt;BR /&gt;Debug-trace logging: enabled&lt;BR /&gt;Console logging: disabled&lt;BR /&gt;Monitor logging: disabled&lt;BR /&gt;Buffer logging: level informational, 922 messages logged&lt;BR /&gt;Trap logging: level informational, facility 20, 1714 messages logged&lt;BR /&gt;Global TCP syslog stats ::&lt;BR /&gt;NOT PUTABLE: 0, ALL CHANNEL DOWN: 0&lt;BR /&gt;CHANNEL FLAP CNT: 0, SYSLOG PKT LOSS: 0&lt;BR /&gt;PARTIAL REWRITE CNT: 0&lt;BR /&gt;Permit-hostdown logging: enabled&lt;BR /&gt;History logging: disabled&lt;BR /&gt;Device ID: disabled&lt;BR /&gt;Mail logging: disabled&lt;BR /&gt;ASDM logging: level informational, 922 messages logged&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 07 Nov 2025 06:32:48 GMT</pubDate>
    <dc:creator>Galle</dc:creator>
    <dc:date>2025-11-07T06:32:48Z</dc:date>
    <item>
      <title>ASA boot/console logs to file</title>
      <link>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345231#M1123415</link>
      <description>&lt;P&gt;I'm planning to update the ASA and ROMMON software on a ISA3000. I've tested it in our lab first and during the testing I've been connected through the console port. This is nice as I can see what is going on during the reload processes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, when I'll perform the upgrade on the target system, I'll only have an SSH connection, no console. Is there a way to get the same messages that can be seen during a reboot with an active console session written to a file? Or how can I get the same info, either live, or downloaded afterwards, from an SSH session?&lt;/P&gt;&lt;P&gt;I've tried to enable syslogging to file, but I can't find any of the messages I'm interested in there. I wondering if the messages I'm interested in do not come from the syslog service?&lt;/P&gt;&lt;P&gt;These are the current log settings:&lt;/P&gt;&lt;PRE&gt;FW01/sec/NoFailover# show logg&lt;BR /&gt;Syslog logging: enabled&lt;BR /&gt;Facility: 20&lt;BR /&gt;Timestamp logging: enabled&lt;BR /&gt;Timezone: enabled&lt;BR /&gt;Logging Format: disabled&lt;BR /&gt;Hide Username logging: enabled&lt;BR /&gt;Standby logging: disabled&lt;BR /&gt;Debug-trace logging: enabled&lt;BR /&gt;Console logging: disabled&lt;BR /&gt;Monitor logging: disabled&lt;BR /&gt;Buffer logging: level informational, 922 messages logged&lt;BR /&gt;Trap logging: level informational, facility 20, 1714 messages logged&lt;BR /&gt;Global TCP syslog stats ::&lt;BR /&gt;NOT PUTABLE: 0, ALL CHANNEL DOWN: 0&lt;BR /&gt;CHANNEL FLAP CNT: 0, SYSLOG PKT LOSS: 0&lt;BR /&gt;PARTIAL REWRITE CNT: 0&lt;BR /&gt;Permit-hostdown logging: enabled&lt;BR /&gt;History logging: disabled&lt;BR /&gt;Device ID: disabled&lt;BR /&gt;Mail logging: disabled&lt;BR /&gt;ASDM logging: level informational, 922 messages logged&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Nov 2025 06:32:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345231#M1123415</guid>
      <dc:creator>Galle</dc:creator>
      <dc:date>2025-11-07T06:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: ASA boot/console logs to file</title>
      <link>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345360#M1123419</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1939086"&gt;@Galle&lt;/a&gt;&amp;nbsp; &amp;nbsp;&amp;gt;....&lt;SPAN&gt;Is there a way to get the same messages that can be seen during a reboot with&lt;BR /&gt;&lt;FONT color="#FF6600"&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; an active console session written to a file?&lt;BR /&gt;&lt;/EM&gt;&lt;FONT color="#000000"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Cisco devices don't support that , well actually it probably involves a number of race conditions&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#FF6600"&gt;&lt;FONT color="#000000"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;What you can do is have&lt;FONT color="#3366FF"&gt; the console&lt;/FONT&gt; connected to a PC with a serial interface, and define a log file&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;in&lt;STRONG&gt; PuTTY&lt;/STRONG&gt; before connecting to the ASA, then reboot&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#FF6600"&gt;&lt;FONT color="#000000"&gt;&amp;nbsp; M.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Nov 2025 16:22:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345360#M1123419</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-11-07T16:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: ASA boot/console logs to file</title>
      <link>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345373#M1123424</link>
      <description>&lt;P&gt;You can't get the boot up messages via SSH because the network services that would allow you to SSH to the device won't start from the very begining. I think what&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291804"&gt;@Mark Elsen&lt;/a&gt;&amp;nbsp;suggested is the only way to work around that.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Nov 2025 16:53:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345373#M1123424</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-11-07T16:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: ASA boot/console logs to file</title>
      <link>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345746#M1123439</link>
      <description>&lt;P&gt;Thank you for the reply. Disappointing that Cisco doesn't provide a boot log on file, something I would consider a normal thing. E.g. there are messages related to configuration settings during boot up that are good to review. We only do console connections to the equipment if absolutely necessary due to difficulties with physical access, and rely on SSH for normal maintenance. And I'm sure qute a large portion of the user base does the same.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Nov 2025 08:21:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345746#M1123439</guid>
      <dc:creator>Galle</dc:creator>
      <dc:date>2025-11-10T08:21:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA boot/console logs to file</title>
      <link>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345751#M1123440</link>
      <description>&lt;P&gt;Yes, I understand that. Logging to file would still be useful!&lt;/P&gt;</description>
      <pubDate>Mon, 10 Nov 2025 08:41:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-boot-console-logs-to-file/m-p/5345751#M1123440</guid>
      <dc:creator>Galle</dc:creator>
      <dc:date>2025-11-10T08:41:41Z</dc:date>
    </item>
  </channel>
</rss>

