<?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 core switch redundancy in Switching</title>
    <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780774#M456835</link>
    <description>&lt;P&gt;hi all, i want to know something about core switch redundancy, when we connect two core switch with stack cable and want to both switch as active active, is it possible? if one switch goes down then what happen? and if both are working then, are they working with by distribute work load with each other.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Mar 2019 01:03:03 GMT</pubDate>
    <dc:creator>Manish Manwal</dc:creator>
    <dc:date>2019-03-09T01:03:03Z</dc:date>
    <item>
      <title>core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780774#M456835</link>
      <description>&lt;P&gt;hi all, i want to know something about core switch redundancy, when we connect two core switch with stack cable and want to both switch as active active, is it possible? if one switch goes down then what happen? and if both are working then, are they working with by distribute work load with each other.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 01:03:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780774#M456835</guid>
      <dc:creator>Manish Manwal</dc:creator>
      <dc:date>2019-03-09T01:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780795#M456840</link>
      <description>Since you mention using a stack cable I will assume that you are levering catalyst 2000 or 3000 series switches.  When two or more switches are stacked, the work is split up between members. The primary (master) as identified in the "show switch" command output.  The master can also be identified from the front panel lights.  &lt;BR /&gt;&lt;BR /&gt;The switches in a stack can all be used to forward traffic, every port is available to configure and use as a normal switch.   If the master switch fails then the next member based on priority takes over the role of master. The new master will have the same configuration and management address. &lt;BR /&gt;&lt;BR /&gt;Where the processing for some functions and features takes place depends on the catalyst model, there have been many revisions of stackwise over the years.  Think of it as a distributed workload, you won't have 24/48 ports of a second switch sitting idle unless the network is configured that way.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Jan 2019 05:35:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780795#M456840</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-01-16T05:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780823#M456845</link>
      <description>&lt;P&gt;adding to other post.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what is the requirement for Active/Active ? what kind of environment is this ?.&lt;/P&gt;
&lt;P&gt;if your end device connected to 1 leg of connection, there is no requirement for Active /Active here design point of view.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but this suggestion based on your input, if you can share your topology and requirement, best can be suggested in this forum&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 06:03:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780823#M456845</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2019-01-16T06:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780829#M456847</link>
      <description>&lt;P&gt;please see the attachment. how we can add redundancy switch. what is the best practice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 06:20:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780829#M456847</guid>
      <dc:creator>Manish Manwal</dc:creator>
      <dc:date>2019-01-16T06:20:57Z</dc:date>
    </item>
    <item>
      <title>Re: core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780842#M456848</link>
      <description>&lt;P&gt;As per your diagram, you do not have redundancy links from Core to Distribution and distribution to Access layer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you looking to re-design your campus design ? I have just added rough connection between cores and also suggested design between distribution to core also.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have also seen the information you have ditribution different location, how are you terminating those connection back to core ? Over VPN ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;more information can be find here :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Campus/CVD-Campus-LAN-WLAN-Design-Guide-2018JAN.pdf" target="_blank"&gt;https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Campus/CVD-Campus-LAN-WLAN-Design-Guide-2018JAN.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 06:36:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780842#M456848</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2019-01-16T06:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780873#M456849</link>
      <description>&lt;P&gt;&lt;BR /&gt;Are you looking to re-design your campus design ?&lt;BR /&gt;ans:- no&lt;BR /&gt;I have also seen the information you have ditribution different location, how are you terminating those connection back to core&lt;BR /&gt;ans :- over fiber links.&lt;BR /&gt;for redundant link from distribution to core we can use another core of fiber link.&lt;BR /&gt;actually, i want to know how we can what is the best way to connect or create redundancy. between core's.&lt;BR /&gt;forget about our network, assume that we are going to create a new network structure, then??&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 08:17:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780873#M456849</guid>
      <dc:creator>Manish Manwal</dc:creator>
      <dc:date>2019-01-16T08:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: core switch redundancy</title>
      <link>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780915#M456853</link>
      <description>&lt;P&gt;I have provided the best option for the cisco best practice, and i have also given CVD, you need to understand the CVD and design as per your requirement.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if you looking all resilence end to end, you need to have all dual links, each level of redundancy, so services will be available all the time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;forget about our network, assume that we are going to create a new network structure, then??&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Follow the cisco Design.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 08:41:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/core-switch-redundancy/m-p/3780915#M456853</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2019-01-16T08:41:39Z</dc:date>
    </item>
  </channel>
</rss>

