<?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 FMCv 7.6 logging issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5277200#M1120400</link>
    <description>&lt;P&gt;We recently upgraded from FMCv7.4.2.1 to 7.6.0.113 and ran into a logging issue (FTD remains at 7.4.2.1). This was after FMCv hung on reboot referencing a Perl script that hung on a database operation. Of course TAC was on the call, we had planned the upgrade proactively with them. After a hour, TAC recommended rebooting which completed the upgrade but now logging is hosed. We typically have about six months of logs but now no matter the query specification, we can only retrieve about six hours of logs. TAC does not have a fix other than to restore back to 7.4.2.1.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We do not have redundant FMCv, but we could if it would help us recover from this scenario, something like this: b&lt;SPAN&gt;uild a new FMCv independently with a fresh database, restore the ACP and other settings separately, bring into HA, etc? T&lt;/SPAN&gt;&lt;SPAN&gt;rying to figure out if this is the best solution. Please advise if you know the details.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 01 Apr 2025 15:01:25 GMT</pubDate>
    <dc:creator>lcaruso</dc:creator>
    <dc:date>2025-04-01T15:01:25Z</dc:date>
    <item>
      <title>FMCv 7.6 logging issue</title>
      <link>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5277200#M1120400</link>
      <description>&lt;P&gt;We recently upgraded from FMCv7.4.2.1 to 7.6.0.113 and ran into a logging issue (FTD remains at 7.4.2.1). This was after FMCv hung on reboot referencing a Perl script that hung on a database operation. Of course TAC was on the call, we had planned the upgrade proactively with them. After a hour, TAC recommended rebooting which completed the upgrade but now logging is hosed. We typically have about six months of logs but now no matter the query specification, we can only retrieve about six hours of logs. TAC does not have a fix other than to restore back to 7.4.2.1.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We do not have redundant FMCv, but we could if it would help us recover from this scenario, something like this: b&lt;SPAN&gt;uild a new FMCv independently with a fresh database, restore the ACP and other settings separately, bring into HA, etc? T&lt;/SPAN&gt;&lt;SPAN&gt;rying to figure out if this is the best solution. Please advise if you know the details.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Apr 2025 15:01:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5277200#M1120400</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2025-04-01T15:01:25Z</dc:date>
    </item>
    <item>
      <title>Re: FMCv 7.6 logging issue</title>
      <link>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5279381#M1120522</link>
      <description>&lt;P&gt;Just to confirm: Is your issue/goal to restore historical data/events or is the FMC simply not retaining data/events beyond 6 hours?&lt;/P&gt;
&lt;DIV id="bodyDisplay_3" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 08 Apr 2025 15:34:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5279381#M1120522</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2025-04-08T15:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: FMCv 7.6 logging issue</title>
      <link>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5279393#M1120524</link>
      <description>Both issues, but we discovered a setting that needed updating for retaining new logs beyond a few hours, so that issue is solved. For the other issue, TAC is advising we restore from backup, or purge, or create a new VM and restore configuration without events.&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Apr 2025 15:53:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmcv-7-6-logging-issue/m-p/5279393#M1120524</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2025-04-08T15:53:04Z</dc:date>
    </item>
  </channel>
</rss>

