<?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 syslog resumption in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/syslog-resumption/m-p/1106194#M893304</link>
    <description>&lt;P&gt;I have a bunch of Cisco ASA unit's all sending tcp based syslog data to a central Kiwi Syslog server.  I have the units configured to continue functioning after syslog communications failure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have patches applied on a regular basis and when the Syslog server is patched/rebooted, it seems that all my firewalls stop sending syslog data b/c of the server boot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there some way to automatically kickstart the ASA's to resume logging?  Right now I have to manually reconfigure each ASA unit to restore syslog data transmission.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running 8.0(3) and ASDM 6.1.1 on a variety of 5510's, 5520's and 5540's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tariq&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 14:15:35 GMT</pubDate>
    <dc:creator>rahmant</dc:creator>
    <dc:date>2019-03-11T14:15:35Z</dc:date>
    <item>
      <title>syslog resumption</title>
      <link>https://community.cisco.com/t5/network-security/syslog-resumption/m-p/1106194#M893304</link>
      <description>&lt;P&gt;I have a bunch of Cisco ASA unit's all sending tcp based syslog data to a central Kiwi Syslog server.  I have the units configured to continue functioning after syslog communications failure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have patches applied on a regular basis and when the Syslog server is patched/rebooted, it seems that all my firewalls stop sending syslog data b/c of the server boot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there some way to automatically kickstart the ASA's to resume logging?  Right now I have to manually reconfigure each ASA unit to restore syslog data transmission.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running 8.0(3) and ASDM 6.1.1 on a variety of 5510's, 5520's and 5540's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tariq&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:15:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syslog-resumption/m-p/1106194#M893304</guid>
      <dc:creator>rahmant</dc:creator>
      <dc:date>2019-03-11T14:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: syslog resumption</title>
      <link>https://community.cisco.com/t5/network-security/syslog-resumption/m-p/1106195#M893305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please try to set up the captures between the ASA and the server then when you reboot the unit enable the logs on the firewall to verify what error do you get also, the capture will let you know at what time the ASA stopped sending the syslog messages.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Nov 2008 21:45:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syslog-resumption/m-p/1106195#M893305</guid>
      <dc:creator>torchris</dc:creator>
      <dc:date>2008-11-23T21:45:39Z</dc:date>
    </item>
  </channel>
</rss>

