<?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 FWSM Active/Active Failover Logging in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135699#M394349</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the documentation for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/fwsm/fwsm40/configuration/guide/monitr_f.html#wp1098808"&gt;http://www.cisco.com/en/US/docs/security/fwsm/fwsm40/configuration/guide/monitr_f.html#wp1098808&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Dec 2012 05:15:31 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2012-12-11T05:15:31Z</dc:date>
    <item>
      <title>FWSM Active/Active Failover Logging</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135696#M394346</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know if during a failover syslog logs or SNMP alerts should be generated on individual FWSM contexts. I have looked through syslogs from the time a failover has occured and I have seen no mention of any failover. Our SNMP management software doesn't report anything either. At the time all contexts other than the admin context were configured for syslog. The admin context was only configured for SNMP, which has now been corrected. Until we see another failover event though I cannot confirm if this has made any difference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main driver for this is that in the event of a failover our NOC does not see a problem. They poll the devices via IP, so unless we were to physically lose a module we do not know a failover has occured as both the active and standby IP addresses are available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:35:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135696#M394346</guid>
      <dc:creator>Andy Robinson</dc:creator>
      <dc:date>2019-03-12T00:35:30Z</dc:date>
    </item>
    <item>
      <title>FWSM Active/Active Failover Logging</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135697#M394347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, syslog for failover will be generated from the admin context because failover configuration is actually configured on system context and system context information will be relayed via admin context.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2012 16:16:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135697#M394347</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-12-10T16:16:45Z</dc:date>
    </item>
    <item>
      <title>FWSM Active/Active Failover Logging</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135698#M394348</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jennifer, thank you for the response, I was having difficulty finding documentation to confirm if this was the case&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2012 16:46:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135698#M394348</guid>
      <dc:creator>Andy Robinson</dc:creator>
      <dc:date>2012-12-10T16:46:33Z</dc:date>
    </item>
    <item>
      <title>FWSM Active/Active Failover Logging</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135699#M394349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the documentation for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/fwsm/fwsm40/configuration/guide/monitr_f.html#wp1098808"&gt;http://www.cisco.com/en/US/docs/security/fwsm/fwsm40/configuration/guide/monitr_f.html#wp1098808&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Dec 2012 05:15:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135699#M394349</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-12-11T05:15:31Z</dc:date>
    </item>
    <item>
      <title>FWSM Active/Active Failover Logging</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135700#M394350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Dec 2012 08:46:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-active-active-failover-logging/m-p/2135700#M394350</guid>
      <dc:creator>Andy Robinson</dc:creator>
      <dc:date>2012-12-11T08:46:16Z</dc:date>
    </item>
  </channel>
</rss>

