<?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: Fault Tolerance not working between CSMs in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016894#M20169</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you resolved this issue as I have something similar?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Jul 2008 10:53:24 GMT</pubDate>
    <dc:creator>g-hopkinson</dc:creator>
    <dc:date>2008-07-18T10:53:24Z</dc:date>
    <item>
      <title>Fault Tolerance not working between CSMs</title>
      <link>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016891#M20166</link>
      <description>&lt;P&gt;I have two CSM modules in two differnt switches (Bridge mode) configured for high availability. After noticing one of the CSM modules was in failed mode, I reset the module. While the module reboots I get the following messages: %CSM_SLB-4-REDUNDANCY_WARN: Module 3 FT warning: LRP: no ACK from standby.. standby may be down&lt;/P&gt;&lt;P&gt; %CSM_SLB-4-TOPOLOGY: Module 3 warning: IP address conflict: ARP frame from 170.41.228.10 with MAC 00:01:64:f9:&lt;/P&gt;&lt;P&gt;1a:07 received on VLAN 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With both online a "show mod csm 3 ft" shows both modules active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can no longer access the real servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I remove the module that I reset (Primary) I can access the servers using the backup CSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whe I remove the backup CSM and insert the Primary, I cannot acces the servers once again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The FT vlan is VLAN 7 configured on both switches and is the only allowed VLAN on the trunk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The config for the Primary CSM is:redundancy&lt;/P&gt;&lt;P&gt; mode sso&lt;/P&gt;&lt;P&gt; main-cpu&lt;/P&gt;&lt;P&gt;  auto-sync running-config&lt;/P&gt;&lt;P&gt;spanning-tree mode pvst&lt;/P&gt;&lt;P&gt;module ContentSwitchingModule 3 &lt;/P&gt;&lt;P&gt; ft group 7 vlan 7 &lt;/P&gt;&lt;P&gt;  priority 30&lt;/P&gt;&lt;P&gt;  preempt &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vlan 2 client&lt;/P&gt;&lt;P&gt;  ip address 170.41.228.20 255.255.255.192&lt;/P&gt;&lt;P&gt; gateway 170.41.228.1&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vlan 8 server&lt;/P&gt;&lt;P&gt;  ip address 170.41.228.20 255.255.255.192&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; probe CARMENWEBPROBE tcp&lt;/P&gt;&lt;P&gt;  interval 10 &lt;/P&gt;&lt;P&gt;  failed 100 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; probe HTTPS tcp&lt;/P&gt;&lt;P&gt;  interval 10 &lt;/P&gt;&lt;P&gt;  failed 100 &lt;/P&gt;&lt;P&gt;  port 443 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; serverfarm CARMENWEBFARM&lt;/P&gt;&lt;P&gt;  nat server&lt;/P&gt;&lt;P&gt;  no nat client&lt;/P&gt;&lt;P&gt;  real 170.41.228.15&lt;/P&gt;&lt;P&gt;   inservice&lt;/P&gt;&lt;P&gt;  real 170.41.228.16&lt;/P&gt;&lt;P&gt;   inservice&lt;/P&gt;&lt;P&gt;  probe HTTPS&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vserver CARMENVSERVER&lt;/P&gt;&lt;P&gt;  virtual 170.41.228.10 tcp 0&lt;/P&gt;&lt;P&gt;  serverfarm CARMENWEBFARM&lt;/P&gt;&lt;P&gt;  persistent rebalance&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trunk for VLAN 7 config :&lt;/P&gt;&lt;P&gt;interface GigabitEthernet4/2&lt;/P&gt;&lt;P&gt; switchport&lt;/P&gt;&lt;P&gt; switchport trunk encapsulation isl&lt;/P&gt;&lt;P&gt; switchport trunk allowed vlan 7&lt;/P&gt;&lt;P&gt; switchport mode trunk&lt;/P&gt;&lt;P&gt; no ip address&lt;/P&gt;&lt;P&gt; logging event link-status&lt;/P&gt;&lt;P&gt; logging event spanning-tree status&lt;/P&gt;&lt;P&gt; logging event trunk-status&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone had this problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Donald&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2008 12:33:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016891#M20166</guid>
      <dc:creator>donald.james</dc:creator>
      <dc:date>2008-04-08T12:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: Fault Tolerance not working between CSMs</title>
      <link>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016892#M20167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you tried to swap cards ?&lt;/P&gt;&lt;P&gt;Take the working standby and move it to the chassis of the not-working active.&lt;/P&gt;&lt;P&gt;See if the problem stick to the card or the chassis.&lt;/P&gt;&lt;P&gt;Then try to use one CSM at a time and use sniffer trace to see if a ping from csm to server get out of the blade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2008 13:53:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016892#M20167</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-04-08T13:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: Fault Tolerance not working between CSMs</title>
      <link>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016893#M20168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The plan is to take a working CSM from a DR site with the same config to try in place of the not working active. I did not want to risk taking the working stanby and moving it and possibly having an outage at this time since this is a production switch being heavily utilized at the moment. I wanted to verify there was not something in the config that was not configured properly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2008 15:06:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016893#M20168</guid>
      <dc:creator>donald.james</dc:creator>
      <dc:date>2008-04-08T15:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: Fault Tolerance not working between CSMs</title>
      <link>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016894#M20169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you resolved this issue as I have something similar?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2008 10:53:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/fault-tolerance-not-working-between-csms/m-p/1016894#M20169</guid>
      <dc:creator>g-hopkinson</dc:creator>
      <dc:date>2008-07-18T10:53:24Z</dc:date>
    </item>
  </channel>
</rss>

