Cisco Catalyst 9500 Configuration Guide, Release 16.6 ...

1 ConfiguringCiscoStackWiseVirtual FindingFeatureInformation, on page 1 Prerequisitesfor Cisco StackWise Virtual, on page 1 Restrictionsfor Cisco StackWise Virtual, on page 1 InformationAbout Cisco StackwiseVirtual, on page 2 How to ConfigureCisco StackWise Virtual, on page 12 VerifyingCisco StackWise Virtual Configuration , on page 20 AdditionalReferencesfor StackWise Virtual, on page 20 FeatureHistoryand Informationfor Cisco StackWise Virtual, on page 21 FindingFeatureInformationYour softwarereleasemay not supportall the featuresdocumentedin this the latest caveatsandfeatureinformation,see Bug SearchTool and the releasenotes for your platformand informationabout the featuresdocumentedin this module,and to see a list of the releasesin which eachfeatureis supported,see the featureinformationtable at the end of this Cisco FeatureNavigatorto find informationabout platformsupportand Cisco softwareimage access Cisco FeatureNavigator, go to An accounton CiscoStackWiseVirtual All the switchesin the Cisco StackWise Virtual solutionshouldbe runningthe same licenselevel.

2 All the switchesin the Cisco StackWise Virtual shouldbe CiscoStackWiseVirtual The maximumnumberof Cisco StackWise Virtual links supportedis eight. Cisco StackWise Virtual is supportedonly on C9500-24 Qswitch models. The dual active and StackWise Virtual link configurationare performeddynamicallyand the deviceshouldbe rebootedafter Only Cisco TransceiverModulesare supported. TheinterfaceVLANMAC addressthatisassignedbydefault, this commandis configuredon a single SVI or router port that requiresLayer 3 injectedpackets,all other SVIs or routed ports on the device also must be configuredwith the same first fourmost significantbits (4 MSB)of the MAC example,if you set the MAC addressof any SVIto , set the MAC addressof all other SVIs to start with If Layer 3 injectedpacketsare not used, this restrictiondoes not appliesto all Layer 3 ports, SVIs, and routed ports.

3 This does not apply toGigabitEthernet0 a Cisco StackWise Virtual solutionsimplifyoperationalefficiencywit h a single controland managementplane, scale systembandwidthwith distributedforwardingplane, and assist in buildingresilientnetworksusing the StackWise Virtual allows two physicalswitchesto operateas a single logicalvirtual switch using a 40-G or 10-G typicalnetworkdesign consistsof core, distribution,and access layers. The defaultmode of a switch two redundantswitchesare deployedin the distributionlayer, the followingnetworkchallengesarise: IfVLANID sarereusedbetweenaccesslayersthen,itwill introduceaspanningtreeloopthatwillimpact the overallperformanceof the network. Spanningtree protcolsand configurationare requiredto protectLayer 2 networkagainstspanningtreeprotcolloop, and root and bridge protocoldata unit management.

4 Additionalprotocolssuch as first hop redundancyprotocolare requiredto virtualizethe IP shouldalign with STP root prioritiesfor each VLAN. The Protocolindependentmulticastdesignatedro uter (PIM DR) configurationshouldbe fine-tunedtoselectivelybuild a multicastforwardingtopologyon a VLAN. The standalonedistributionlayer systemprovidesprotocol-drivenremotefailu re and detection, The Cisco StackWise technologyis a technology, which,when extendedover Ethernetnetworks,providesflexibilitysinc e the length of the traditionalback stack cable is not a stackConfiguringCiscoStackWiseVirtual2 ConfiguringCiscoStackWiseVirtualInformat ionAboutCiscoStackwiseVirtualcan be formedover a redundant40-G or 10-G fiber links to ensure that the distributionor the aggregationswitchescan be deployedover a large that STP keeps one of the ports connectedto the distributionswitchesblockedon the access a result of this, an active link failure causes STP convergence and the networksuffers from traffic loss,flooding.

5 And a possibletransientloop in the the other hand, if the switchesare logicallymergedinto one switch,all the access switchesmight form an EtherChannelbundlewith distributionswitches,anda link failure within an EtherChannelwould not have any impactas long as at least one memberwithin theEtherChannelis : TypicalNetworkDesignusingCiscoStackWiseV irtualEtherchannelin StackWise Virtual is capableof implementingMEC across the stack accesslayer and aggregationlayer are collapsedinto a single StackWise Virtual system,MEC across the differentaccess layer domainmembersand across distributionand access layer switcheswill not be designedto forwardthe traffic over the local link irrespectiveof the hash the controlplane, managementplane, and data plane are integrated,the systembehavesas a perspectiveonly.

6 Becauseof the controlplane being common,it may look like a single logicalentityto peer data plane of the switchesare switch is capableof forwardingover itslocal interfaceswithoutinvolvingother , when a packet cominginto a switch has to beforwardedoveradifferentmember sport, ,thecommoncontrolplaneensuresthatallthes witcheshave equivalentdata plane entry for each electionmechanism,which elects one of the switchesto be Cisco StackWise Virtual active and the otherswitchtobeacontrolplanestandby, ,bridgingand routingprotocols,and softwaredata path. These are centralizedon the ActiveSupervisorof aCisco StackWise Virtual active StackWise Virtual memberswitchestalk to each other using a virtual softwaremodulecalled VirtualCommunicationManager(VCM ) over a StackWise Virtual followingare the componentsof the Cisco StackWise Virtual solution:ConfiguringCiscoStackWiseVirtua l3 ConfiguringCiscoStackWiseVirtualCiscoSta ckWiseVirtualTopology Stack members StackWise Virtual link: 10-Gb or 40-Gb , You can configureany physicalport as a StackWise Virtual link.

7 When a switch is poweredup and thehardwareis initiliazed,it looks for a configuredStackWise Virtual link before the initilizationof the (SVH)is64-byteoverheadframethatisappende doverallcontrol,data,andmanagementplanet rafficthattraverseovereachSVLbetweenthet wostackmembersoftheCiscoStackWiseVirtual SVH-encapsulatedtraffic operatesat OSI Layer 2 and can be recognizedand ,andallowsnonrouteabletraffic over a L2 or L3 StackWise Virtual operatesstatefulswitchover(SSO) betweenthe active and 'sredundancymodeldiffersfromthatofthesta ndalonemode: The Cisco StackWise Virtual active and standbyswitchesare hosted in separateswitchesand use aStackWise Virtual link to exchangeinformation. The active switch controlsboth the switchesof Cisco StackWise Virtual.

8 The active switch runs theLayer 2 and Layer 3 controlprotocolsand managesthe switchingmodulesof both the switches. The Cisco StackWise Virtual active and standbyswitchesperformdata traffic the Cisco StackWise Virtual active switch fails, the standbyswitch initiatesa switchoverand assumestheCisco StackWise Virtual active switch StackWise Virtual systemoperateswith SSO redundancyif it meets the followingrequirements: Both the switchesmust be runningthe same softwareversion,unless they are in the processof softwareupgrade. StackWise Virtual link-relatedconfigurationin the two switchesmust match. Non-Stopforwarding(NSF) configurationshouldnot be dependenton buildingSSO peering. Licensetype must be same on both the switch models.

9 Both the switch modelsmust be in the same StackWise Virtual SSO redundancy, the StackWise Virtual standbyswitch is alwaysready to assumecontrolif a faultoccurs on the StackWise Virtual active ,forwarding,and state informationaresynchronizedfrom the StackwiseVirtual active switch to the redundantswitch at startup,and wheneverConfiguringCiscoStackWiseVirtual 4 ConfiguringCiscoStackWiseVirtualCiscoSta ckWiseVirtualRedundancychangesto the StackWise Virtual active switch configurationoccur. If a switchoveroccurs,traffic disruptionis StackWise Virtual does not meet the requirementsfor SSO redundancy, it will be incapableof establishinga relationshipwith the peer Virtual runs statefulswitchover(SSO) betweenthe StackWiseVirtual active and StackWise Virtual determinesthe role of each switch link to synchronizeconfigurationdata from the StackWise Virtual active switch to the StackWiseVirtual , protocolsand featuresthat supporthigh availabilitysynchronizetheir eventsand state informationto the StackWise Virtual (NSF)

10 TechnologyinsystemsusingSSOredundancymod e,networkdisruptionsare transparentto campususers and availabilityis providedeven when , preset forwardinginformationon theredundantstack-memberswitchremainsint act;this switchcontinuesto forwardthe datain the (MTTR)andincreasesthemeantimebetweenfail ure (MTBF)to achievea high level of (MEC)is an EtherChannelbundledwith physicalports havingcommoncharacteristicssuch as speed and duplex,that are distributedacross each Cisco StackWise Virtual StackWise Virtual MEC can connectto any networkelementthat supportsEtherChannel(such as ahost, server, router, or switch). Cisco StackWise Virtual supportsup to 128 MECs deployedin Layer 2 orLayer 3 is reservedfor SVL ,the maximumavailableMECcount is a Cisco StackWise Virtual system,an MEC is an EtherChannelwith additionalcapability.