<?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 and spanning tree in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374527#M6471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I looked at the diagram.&lt;/P&gt;&lt;P&gt;May be if you remove the cross connect (X, X) you will still get redundancy and probably avoid spanning tree. Let me know the outcome.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Apr 2005 11:24:19 GMT</pubDate>
    <dc:creator>s.srivas</dc:creator>
    <dc:date>2005-04-29T11:24:19Z</dc:date>
    <item>
      <title>CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374512#M6456</link>
      <description>&lt;P&gt;i'm slowing building the CSS ASR configuration and currently have &lt;/P&gt;&lt;P&gt;           Private&lt;/P&gt;&lt;P&gt;             |&lt;/P&gt;&lt;P&gt;          Switch&lt;/P&gt;&lt;P&gt;          /    \&lt;/P&gt;&lt;P&gt;master&amp;gt; CSS----CSS &amp;lt;backup&lt;/P&gt;&lt;P&gt;         \     /&lt;/P&gt;&lt;P&gt;          Switch&lt;/P&gt;&lt;P&gt;            |&lt;/P&gt;&lt;P&gt;         Public&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i plan to add 2 more L2 switches to the 1 in pub area and 1 in priv area. i have the CSS vr peering configured and showing up correctly as master and back up  front and back. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is that will some additional spanning tree configuration have to be (done/looked at) with the additional switches in &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2005 15:37:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374512#M6456</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-22T15:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374513#M6457</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;What are you stating as the additional switches? The css's?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;==DMT&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Apr 2005 18:10:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374513#M6457</guid>
      <dc:creator>dtodd</dc:creator>
      <dc:date>2005-04-23T18:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374514#M6458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in the private area will be 3550 or 3750.. on the public area it will either be 3550 or a 4000 series.. 2 switch connections in front and back for redundancy.. the css will be using ASR those are in the middle using 11506.. from all my checking it works in th current one access switch level but the concern is when spanning tree picks the best path that is pick the master css.. &lt;/P&gt;&lt;P&gt;i noticed from a trace the master was sending vrrp messages which i think should resolve the prob but i'm unsure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Apr 2005 20:42:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374514#M6458</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-23T20:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374515#M6459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if you double the number of switches I would recommend not to connect each CSS to each switch.&lt;/P&gt;&lt;P&gt;This has proven to be source of trouble due to spanning-tree.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; SW1 ------ trunk -------SW2&lt;/P&gt;&lt;P&gt; |.......................|&lt;/P&gt;&lt;P&gt; CSS1...................CSS2&lt;/P&gt;&lt;P&gt; |.......................|&lt;/P&gt;&lt;P&gt; SW3------- Trunk ------SW4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the link between SW1 and CSS1, let the CSS fails over instead of relying on spanning-tree.&lt;/P&gt;&lt;P&gt;This solutions works better from past experience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Apr 2005 08:21:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374515#M6459</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-04-25T08:21:45Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374516#M6460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if i'm understanding you correctly.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;only have 1 switch front and back per CSS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the Backup CSS would have the same configuration the only common link the CSS's would be is the isc port..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;once it (the backup)notices the master goes down via isc the ports for the back up would become active &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Apr 2005 17:54:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374516#M6460</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-25T17:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374517#M6461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Even I do not understand what Gilles says, assuming Gilles said that, what if the pri css goes complete dead?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we did was that connect the Server interfaces to L2/L3 switches using NIC teaming. An L2/L3 port is connected to each CSS. Between the L2/L3 run the Etherchannel or Stack GBIC/trunk. It works fine since for a while ago. We had issues intialy like the MAC adress table got flodding on the L2/L3 switches, belive me we came out of that after enabling 'portfast' on the CSS ports and on the connected L2/L3 SW ports, I know its foolish but for some reason it works fine now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Server1&lt;/P&gt;&lt;P&gt;    /       \----&amp;gt;NIC Teaming&lt;/P&gt;&lt;P&gt;  /           \&lt;/P&gt;&lt;P&gt;Sw1---Etherch---Sw2&lt;/P&gt;&lt;P&gt;/                 \ &lt;/P&gt;&lt;P&gt;master&amp;gt;CSS---isc---CSS&lt;BACKUP&gt;&lt;/BACKUP&gt;&lt;/P&gt;&lt;P&gt;\&lt;/P&gt;&lt;P&gt;Switch &lt;/P&gt;&lt;P&gt;| &lt;/P&gt;&lt;P&gt;Public &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Apr 2005 23:42:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374517#M6461</guid>
      <dc:creator>skumar1969</dc:creator>
      <dc:date>2005-04-25T23:42:46Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374518#M6462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if the primary CSS goes down completely, the backup will take over and it will have access to all servers through the switch it is connected to.&lt;/P&gt;&lt;P&gt;This is the easiest solution and a good solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I spent too many hours trying to explain to some people why their highly redundant network failed because of spanning-tree.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution I suggest will provide good redundancy and is quite simple so avoiding problems.&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, 26 Apr 2005 07:38:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374518#M6462</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-04-26T07:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374519#M6463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the ISC port is not used to detect if the master is active or not.&lt;/P&gt;&lt;P&gt;It is just used to send stateful information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The CSS will use VRRP on each link to establish mastership and detect that devices are alive or not.&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, 26 Apr 2005 07:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374519#M6463</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-04-26T07:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374520#M6464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i'm posting a drawing just to be clear on what you've said. if i'm incorrect please modify it beacuse these stick lettering is killing me..lol&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2005 12:12:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374520#M6464</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-26T12:12:44Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374521#M6465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;could you resend as jpeg ?&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;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2005 17:32:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374521#M6465</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-04-26T17:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374522#M6466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;not a prob&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2005 19:20:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374522#M6466</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-26T19:20:09Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374523#M6467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so you use 2 vlans on the public side and 2 vlans on the private side ?&lt;/P&gt;&lt;P&gt;This is ok, just more complex.&lt;/P&gt;&lt;P&gt;You'll need routes pointing to each vlan ip address for the vips.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All I can suggest is to find a solution where you can turn off spanning-tree on the CSS and avoid any routing protocols.&lt;/P&gt;&lt;P&gt;If you can do this, you will avoid potentially a lot of  trouble.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2005 06:24:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374523#M6467</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-04-27T06:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374524#M6468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"so you use 2 vlans on the public side and 2 vlans on the private side ? "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i believe i will have to due to the use of terminal services used to manage servers. so i would have to have an internal vip address for terminal svc to access the servers directly. bypassing the public 'www'vip that outside users would use to access the  stuff.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now when creating that internal vip setting to a vlan it.&lt;/P&gt;&lt;P&gt;would have to a redundant interface?&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;is there no command to turn off spanning-tree on css?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2005 12:09:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374524#M6468</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-27T12:09:12Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374525#M6469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To turn off spanning-tree :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSS11503(config)# bridge spanning-tree disabled&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2005 12:46:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374525#M6469</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-04-27T12:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374526#M6470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for all the help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i will try the spanning-tree command if after adding the extra switches creates a problem&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2005 13:13:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374526#M6470</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-04-27T13:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374527#M6471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I looked at the diagram.&lt;/P&gt;&lt;P&gt;May be if you remove the cross connect (X, X) you will still get redundancy and probably avoid spanning tree. Let me know the outcome.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Apr 2005 11:24:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374527#M6471</guid>
      <dc:creator>s.srivas</dc:creator>
      <dc:date>2005-04-29T11:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374528#M6472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i hadn't gotten quite to the ether channel connections but i deceide not to go with it and also disabled spanning-tree on the css after noticing alot of spanning tree anouncements every 2-10ths of a second&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2005 14:07:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374528#M6472</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-05-04T14:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and spanning tree</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374529#M6473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i hadn't gotten quite to the ether channel connections but i deceide not to go with it and also disabled spanning-tree on the css after noticing alot of spanning tree anouncements every 2-10ths of a second&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2005 14:09:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-spanning-tree/m-p/374529#M6473</guid>
      <dc:creator>kejeusa</dc:creator>
      <dc:date>2005-05-04T14:09:29Z</dc:date>
    </item>
  </channel>
</rss>

