<?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 Re: FWSM Lost Failover communications with mate in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404879#M857166</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;minmin5063 wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I experinced critical problem for our customer service pertaing to communication fail for FT between FWSMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can just find the log in FWSM as follows and can't find any physical log as interface down in C6500 at that moment.&lt;/P&gt;&lt;P&gt;Now our FWSM OS version is 3.2(7) and jsut monitor-interface option is applied at outside interface in FWSM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Main FWSM&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Feb 13 2010 01:49:19|105005: (Secondary) Lost Failover communications with mate on interface statelink&lt;BR /&gt;1|Feb 13 2010 01:49:20|105004: (Secondary) Monitoring on interface statelink normal&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Backup FWSM&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Feb 13 2010 01:49:17|105005: (Primary) Lost Failover communications with mate on interface statelink&lt;BR /&gt;1|Feb 13 2010 01:49:22|105004: (Primary) Monitoring on interface statelink normal&lt;BR /&gt;1|Feb 13 2010 01:51:24|105005: (Primary) Lost Failover communications with mate on interface outside&lt;BR /&gt;1|Feb 13 2010 01:51:24|105008: (Primary) Testing Interface outside&lt;BR /&gt;1|Feb 13 2010 01:51:24|105009: (Primary) Testing on interface outside Passed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our problem is recovered automatically after 2m ~ 3m but that is reoccured after 1 day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already opend the TAC case (SR 613646199)&amp;nbsp; but I didn't get any correct cause for problem and they just recommend to change the FWSM through RMA.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Any advice for our problem whould be greatly appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Sungmin Cho&lt;/SPAN&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sungmin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the FWSM have a dedicated link between the 6500 switches or are you using the interconnect that all the other traffic uses as well ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using the same interconnect as other traffic it could be worth trying to setup a dedicated interconnect just for the FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Feb 2010 10:35:46 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2010-02-17T10:35:46Z</dc:date>
    <item>
      <title>FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404878#M857165</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I experinced critical problem for our customer service pertaing to communication fail for FT between FWSMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can just find the log in FWSM as follows and can't find any physical log as interface down in C6500 at that moment.&lt;/P&gt;&lt;P&gt;Now our FWSM OS version is 3.2(7) and jsut monitor-interface option is applied at outside interface in FWSM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline; "&gt;Main FWSM&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Feb 13 2010 01:49:19|105005: (Secondary) Lost Failover communications with mate on interface statelink&lt;BR /&gt;1|Feb 13 2010 01:49:20|105004: (Secondary) Monitoring on interface statelink normal&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline; "&gt;Backup FWSM&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Feb 13 2010 01:49:17|105005: (Primary) Lost Failover communications with mate on interface statelink&lt;BR /&gt;1|Feb 13 2010 01:49:22|105004: (Primary) Monitoring on interface statelink normal&lt;BR /&gt;1|Feb 13 2010 01:51:24|105005: (Primary) Lost Failover communications with mate on interface outside&lt;BR /&gt;1|Feb 13 2010 01:51:24|105008: (Primary) Testing Interface outside&lt;BR /&gt;1|Feb 13 2010 01:51:24|105009: (Primary) Testing on interface outside Passed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our problem is recovered automatically after 2m ~ 3m but that is reoccured after 1 day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already opend the TAC case (SR 613646199)&amp;nbsp; but I didn't get any correct cause for problem and they just recommend to change the FWSM through RMA.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Any advice for our problem whould be greatly appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Sungmin Cho&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:10:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404878#M857165</guid>
      <dc:creator>Sung Min Cho</dc:creator>
      <dc:date>2019-03-11T17:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404879#M857166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;minmin5063 wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I experinced critical problem for our customer service pertaing to communication fail for FT between FWSMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can just find the log in FWSM as follows and can't find any physical log as interface down in C6500 at that moment.&lt;/P&gt;&lt;P&gt;Now our FWSM OS version is 3.2(7) and jsut monitor-interface option is applied at outside interface in FWSM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Main FWSM&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Feb 13 2010 01:49:19|105005: (Secondary) Lost Failover communications with mate on interface statelink&lt;BR /&gt;1|Feb 13 2010 01:49:20|105004: (Secondary) Monitoring on interface statelink normal&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Backup FWSM&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Feb 13 2010 01:49:17|105005: (Primary) Lost Failover communications with mate on interface statelink&lt;BR /&gt;1|Feb 13 2010 01:49:22|105004: (Primary) Monitoring on interface statelink normal&lt;BR /&gt;1|Feb 13 2010 01:51:24|105005: (Primary) Lost Failover communications with mate on interface outside&lt;BR /&gt;1|Feb 13 2010 01:51:24|105008: (Primary) Testing Interface outside&lt;BR /&gt;1|Feb 13 2010 01:51:24|105009: (Primary) Testing on interface outside Passed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our problem is recovered automatically after 2m ~ 3m but that is reoccured after 1 day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already opend the TAC case (SR 613646199)&amp;nbsp; but I didn't get any correct cause for problem and they just recommend to change the FWSM through RMA.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Any advice for our problem whould be greatly appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Sungmin Cho&lt;/SPAN&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sungmin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the FWSM have a dedicated link between the 6500 switches or are you using the interconnect that all the other traffic uses as well ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using the same interconnect as other traffic it could be worth trying to setup a dedicated interconnect just for the FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Feb 2010 10:35:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404879#M857166</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-02-17T10:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404880#M857167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We already divided the links between C6500s for FT (Regular and Stateful Failover) and data.&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;Sungmin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Feb 2010 10:54:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404880#M857167</guid>
      <dc:creator>Sung Min Cho</dc:creator>
      <dc:date>2010-02-17T10:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404881#M857169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have seen similar issues due to defect CSCsl39710.&lt;/P&gt;&lt;P&gt;Make sure you are running a code on the switch side where this is resolved.&lt;/P&gt;&lt;P&gt;Also, make sure the blade is not seeing more traffic than it can handle at any given time. If so, icmp will be given lower priority and interface monitoring may fail as ping test is one of them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Feb 2010 15:28:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404881#M857169</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-02-17T15:28:33Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404882#M857171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;KS,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all, thank you for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The followinfg is mac-address-table at that time the problem occured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*&amp;nbsp; 903&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;/P&gt;&lt;P&gt;* 1127&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;/P&gt;&lt;P&gt;* 1121&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;/P&gt;&lt;P&gt;* 1101&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;* 1100&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;/P&gt;&lt;P&gt;*&amp;nbsp; 174&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 175&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 180&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 178&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 5&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 177&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 191&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 189&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;BR /&gt;*&amp;nbsp; 187&amp;nbsp; 001a.6c3d.9200&amp;nbsp;&amp;nbsp; dynamic&amp;nbsp; Yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; Po273&lt;/P&gt;&lt;P&gt;.................................................................................&lt;/P&gt;&lt;P&gt;.................................................................................&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We think that C6500 properly learned the MAC address of the FWSM at that moment.&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;Sungmin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Feb 2010 07:38:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404882#M857171</guid>
      <dc:creator>Sung Min Cho</dc:creator>
      <dc:date>2010-02-18T07:38:26Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404883#M857173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm with problems the FWSM in communication for management interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically the setup is correct, but I have had the record of the logs with a frequency below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Main FWSM&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Dec 17 2010 13:01:41|105009: &lt;/SPAN&gt;&lt;SPAN style="font-size: 8pt;"&gt;(Secondary_group_2)&lt;/SPAN&gt;&lt;SPAN style="font-size: 8pt;"&gt; Testing on interface MANAGEMENT Passed&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Dec 17 2010 13:01:37|105008: &lt;/SPAN&gt;&lt;SPAN style="font-size: 8pt;"&gt;(Secondary)&lt;/SPAN&gt;&lt;SPAN style="font-size: 8pt;"&gt; Testing Interface MANAGEMENT&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 8pt;"&gt;1|Dec 17 2010 13:01:36|105005: (Secondary_group_2) Lost Failover communications with mate on interface MANAGEMENT&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWSM Version 4.1(3)&lt;/P&gt;&lt;P&gt;Catalyst 6509 Version 12.2(33).SXI4a &lt;!--[if gte mso 9]&gt;&lt;xml&gt; &lt;o:OfficeDocumentSettings&gt; &lt;o:RelyOnVML&gt;&lt;/o:RelyOnVML&gt; &lt;o:AllowPNG&gt;&lt;/o:AllowPNG&gt; &lt;/o:OfficeDocumentSettings&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;SPAN style="font-family: arial,helvetica,sans-serif;"&gt;&lt;SPAN lang="EN-US" style="font-size: 8pt; line-height: 150%; font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #8683a4; letter-spacing: 0.5pt;"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could anyone suggest something?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Dec 2010 18:32:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404883#M857173</guid>
      <dc:creator>Rafael Trujilho</dc:creator>
      <dc:date>2010-12-17T18:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404884#M857175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only lasts for 5 seconds and then quickly recovers.&lt;/P&gt;&lt;P&gt;It may be a busy interface. You can try to capture all traffic (IP protocol 105) on this interface on both the units when the problem occurs and see why what one unit sends doesn't arrive on the other unit and the interface goes into testing mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Dec 2010 02:15:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404884#M857175</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-12-18T02:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404885#M857177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi KS,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Considering that the device is an FWSM, it could mean a hardware problem?&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;Trujilho&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Dec 2010 16:32:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404885#M857177</guid>
      <dc:creator>Rafael Trujilho</dc:creator>
      <dc:date>2010-12-20T16:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404886#M857179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We've just experienced what seems to be the exact same thing.&lt;/P&gt;&lt;P&gt;Did you get a resolution to this ? How did you go with the TAC case ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Phill.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2011 23:09:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404886#M857179</guid>
      <dc:creator>phillchannon</dc:creator>
      <dc:date>2011-03-29T23:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404887#M857180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How was this resolved ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As we are now seeing the same issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Apr 2011 10:24:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404887#M857180</guid>
      <dc:creator>Ian Beck</dc:creator>
      <dc:date>2011-04-12T10:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Lost Failover communications with mate</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404888#M857181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Found my issue :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Caused by a static NAT using the Firewall Interface as the NAT Addrees, changed it to a assigned IP Address and the problem went away !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Apr 2011 11:13:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-lost-failover-communications-with-mate/m-p/1404888#M857181</guid>
      <dc:creator>Ian Beck</dc:creator>
      <dc:date>2011-04-12T11:13:42Z</dc:date>
    </item>
  </channel>
</rss>

