#Controlplane mac alternative how to
#Controlplane mac alternative full
#Controlplane mac alternative software
#Controlplane mac alternative series

Pictured below the Switch Virtual Links are the Active Optical Cables with 40G QSFPs. So this is a high speed, high bandwidth connection. The Switch Virtual link is used send control plane and data plane traffic between the two switches. There’s two connections for the Switch Virtual Link, and two connections for the Dual Active Detection. You’ll also need to make the connections between the switch pairs.

#Controlplane mac alternative full

17.2.1 will make full use of all four supervisor cards. So if you lose a sup card in a chassis then Stackwise will failover to the other chassis until the failed sup card is replaced. If you dual sup cards per chassis and running a version of IOS previos to 17.2.1 then one sup card in each chassis will just not be used. I think it’s important to add here that the quad-sup support is not built-in until 17.2.1. If you need/want quad supervisor card support you’ll need IOS-XE 17.2.1 or newer.

16.12.1 or newer on the Catalyst 9606 chassis switches – this is dual sup support only – so only one sup card per chassis.

#Controlplane mac alternative series

16.9.1 or newer on the Catalyst 9400 series.16.8.1 or newer provides support for the Catalyst 3850XS and all 9500 series switches.

#Controlplane mac alternative software

There are some software requirements for Stackwise-Virtual depending on the hardware platform you’re going to be running. With Stackwise the rest of the network will see these two redundant switches as a single logical switch hosting the L2/元 boundary, and no need to implement FHRP configuration so we can IP address space/utilization. If we didn’t use Stackwise then we would have to give some additional attention to Spanning Tree, and perhaps add in a First Hop Redundancy Protocol like VRRP or HSRP. We can also take advantage of Control and Management Plane redudancy features like ISSU and Non-Stop Forwarding.

We can load balance aggregated links across the two different physical switches. Why use Stackwise? Well with Stackwise we can address a redundant pair of switches as a single logical switch, rather than manage two separate switches. With Stackwise-Virtual, and the older VSS, you have two physical switches but you were logically managing a single a switch, just as you would with physically stacked switches. You’re logically managing two separate switches.

This is not to be confused with the Nexus VPC – the major difference here is that with Nexus VPC the switches still operate independently of each other from a control and management plane perspective. If you ran the tride and true 6K or 4500 series platform you may recall the Virtual Switch System, or VSS, which did the same thing. Stack-wise virtual is how we connect switches that lack the physical stack ports found on the 9300 and older 3K series, and some 2900 series switches. So, a whole stack of switches can now be controlled as a single switch. While logically they are many switches, from a control plane standpoint they function as a single switch. You can physically, or virtually, stack switches so their control plane and MAC tables combine. Let’s start at the the beginning and answer the question – what is Stack-wise Virtual? Stacking has been around forever in the Catalyst lineup.

#Controlplane mac alternative how to

So, I thought I’d take some time to share with you what exactly is Stack-wise Virtual, how to configure it, and some of the caveats I’ve found in the process. The design calls for Stack-wise virtual on 96 series switches. Lately I’ve been configuring and deploying a lot of Cisco Catalyst 9K series switches. Stack-wise Virtual with Catalyst 9K Switches! A pair of Cisco Cat9K 9500’s I was preparing for Stack-wise.