<?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: CSS issue in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-issue/m-p/743195#M14239</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;looks like an interface issue.&lt;/P&gt;&lt;P&gt;do a 'sho phy' on both css and a 'show int gig x/x/x' on the catalyst.&lt;/P&gt;&lt;P&gt;Verify if the interface is up/up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Connect a pc in the same subnet and try to ping it from both CSS.  See which one fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Send us the output of the show phy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 May 2007 08:36:38 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2007-05-18T08:36:38Z</dc:date>
    <item>
      <title>CSS issue</title>
      <link>https://community.cisco.com/t5/application-networking/css-issue/m-p/743194#M14238</link>
      <description>&lt;P&gt;We have a pair of CSS (model 11503) configured as an active/standby pair using redundant VIPs and interfaces. Each CSS has connections to the same four subnets for which one CSS is the Master and the other Backup. &lt;/P&gt;&lt;P&gt;This all works fine but when I recently connected another gigabit interface on each CSS to a new subnet, the two CSS failed to see each other and both came up as Master. To eliminate the switches they were connected to as the possible cause, I reconnected them to a single standalone switch but the same problem resulted. The CSS could not ping each others interface either. I think it could be something to do with ARP entries and collected the information below. &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;&lt;P&gt;On what should be the Master CSS: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh arp &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.185.2.20 00-0e-d7-c7-9f-19 dynamic 3/2 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh virt &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface Address: 10.185.2.10 VRID: 100 &lt;/P&gt;&lt;P&gt;Priority: 254 Config. Priority: 254 &lt;/P&gt;&lt;P&gt;State: Master Master IP: &lt;/P&gt;&lt;P&gt;10.185.2.10 &lt;/P&gt;&lt;P&gt;State Changes: 9 Last Change: 05/16/2007 &lt;/P&gt;&lt;P&gt;06:23:08 &lt;/P&gt;&lt;P&gt;Preempt: False Last Fail Reason: Critical &lt;/P&gt;&lt;P&gt;Phy Down &lt;/P&gt;&lt;P&gt;Last Clearing of Stat Counters: 05/10/2007 18:16:07 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Critical-Reporters: &lt;/P&gt;&lt;P&gt;css-failover-3 State: Up Type: &lt;/P&gt;&lt;P&gt;critical-phy-all-up &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;&lt;P&gt;On what should be the Backup CSS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh arp &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.185.2.10 00-0e-d7-c7-9e-18 dynamic 3/2 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh virt &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface Address: 10.185.2.20 VRID: 100 &lt;/P&gt;&lt;P&gt;Priority: 253 Config. Priority: 253 &lt;/P&gt;&lt;P&gt;State: Master Master IP: &lt;/P&gt;&lt;P&gt;10.185.2.20 &lt;/P&gt;&lt;P&gt;State Changes: 12 Last Change: 05/16/2007 &lt;/P&gt;&lt;P&gt;06:24:20 &lt;/P&gt;&lt;P&gt;Preempt: False Last Fail Reason: Critical &lt;/P&gt;&lt;P&gt;Phy Down &lt;/P&gt;&lt;P&gt;Last Clearing of Stat Counters: 05/10/2007 18:18:40 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Critical-Reporters: &lt;/P&gt;&lt;P&gt;css-failover-3 State: Up Type: &lt;/P&gt;&lt;P&gt;critical-phy-all-up &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;&lt;P&gt;On the 3750M switch they both connect to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 0000.5e00.0164 DYNAMIC Gi1/0/1 &lt;/P&gt;&lt;P&gt;1 000e.d7c7.9e18 DYNAMIC Gi1/0/1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed there was no entry for 000e.d7c7.9f19 which I would have expected to see. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Packets are being sent and received between the ports&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 May 2007 22:46:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-issue/m-p/743194#M14238</guid>
      <dc:creator>mayambanzumba</dc:creator>
      <dc:date>2007-05-17T22:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: CSS issue</title>
      <link>https://community.cisco.com/t5/application-networking/css-issue/m-p/743195#M14239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;looks like an interface issue.&lt;/P&gt;&lt;P&gt;do a 'sho phy' on both css and a 'show int gig x/x/x' on the catalyst.&lt;/P&gt;&lt;P&gt;Verify if the interface is up/up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Connect a pc in the same subnet and try to ping it from both CSS.  See which one fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Send us the output of the show phy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 08:36:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-issue/m-p/743195#M14239</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2007-05-18T08:36:38Z</dc:date>
    </item>
  </channel>
</rss>

