My issue with it is they say the 9500 can be stacked for 96 port density. But if you use the SVL for port density there is no way to SVL two more 9500's Basically you can't have a 4x switch 96 port redundant stack. Very limiting IMO.
Redundant SVL and DAD links are recommended for completing StackWise Virtual Configuration between the switches. I had few questions around this: 1. Is Cisco StackWise Virtual feasible between more than 2 switches? 2. Say, I was planning to implement StackWise Virtual Configuration between two or three switches, can you please provide a sample configuration of how this would look and what the physical connectivity between the switches should be. 3. What would be the potential Cisco StackWise Virtual throughput difference between using Hundred GigE, Forty Gigabit Ethernet or Twenty Five GigE interface for SVL links between switches? 4. Is there a future plan to introduce Graceful Insertion and Removal for the C9500-32C, C9500-32QC, C9500-48Y4C, and C9500-24Y4C models of the Cisco Catalyst 9500 Series Switches? Thank you.
We recommend checking out our Cisco Switching Community: community.cisco.com/t5/switching/bd-p/6016-discussions-lan-switching-routing, where you can connect with peers and switching experts who can answer your technical questions. Thanks!
Mark van Veelen its recommended to use higher speed links for VSL in a redundant fashion as it’s a fallback in case you need to have data plane traffic traverse it. The purpose of the dual active detection is about detecting conflicts in configuration and state of the two chassis. It doesn’t require much bandwidth at all, even a 1Gbps link will do for it, again deploying this in a redundant format is recommended. So in summary use 2x10Gbps or 2x40Gbps for the VSL and 2x1Gbps or 2x10Gbps for dual active detection. HTH
from the text book approach, what ever is configured on the physical interfaces has to match the channel that you grouped them into, if you have mismatches between the physical and the Po then you will run into issues, what i have seen on the field on the latest OS, is changes made to the Po automatically get pushed to the physical interfaces, but if you change something on the physical interface then the interface will exit the Po membership.
In a regular stackwise setup ive connected switches like A->B->C->D->A so that a cable/switch could fail in the middle and the stack still has full communication. (A and D would the uplinks to the core) Does this work with virtual stackwise? Would you need a dual active detection link in this case?
Yes, it is recommended to have DAD links in SVL setup because you are using front panel ports with regular cabling for stacking switches compared to back stacking which uses dedicated ports with dedicated cables in a ring fashion.
several links in a SVL is recommended but not illustrated in the video or comments (or anywhere it seems in fact). Can you configure several links in a SVL with an interface range command ? as in : Device(config)#interface range FortyGigabitEthernet1/0/1 ,FortyGigabitEthernet1/0/2 Device(config-if)#stackwise-virtual link 1 or Do yo have to configure several SVL ID numbers like in : Device(config)#interface range FortyGigabitEthernet1/0/1 Device(config-if)#stackwise-virtual link 1 Device(config-if)#interface range FortyGigabitEthernet1/0/2 Device(config-if)#stackwise-virtual link 2 It is too bad since it is what is recommended it is not shown as an example somewhere
can we configure VSL and Dual-Active-Detection both on single link on 9407 R Chessis switchs.(bandwidth of link is 10 gig). if yes, then would it work properly if one switch goes down . please reply me as soon as posible.
WHY?!? Why does this have annoying music running at the same volume as the speaker? I have to try to hear & understand his accent while it's being masked by that infernal music. Again, Why? I had to kill the volume and just go with the subtitles (I hope they're right). Another d@m^ed video made strictly in the Marketing Department! Very tempted to just down vote...
This seems very similar to VSS on Cat6k, is there a difference?
Richard Gallagher conceptually the same and end result is the same too.
My issue with it is they say the 9500 can be stacked for 96 port density. But if you use the SVL for port density there is no way to SVL two more 9500's Basically you can't have a 4x switch 96 port redundant stack. Very limiting IMO.
Redundant SVL and DAD links are recommended for completing StackWise Virtual Configuration between the switches. I had few questions around this:
1. Is Cisco StackWise Virtual feasible between more than 2 switches?
2. Say, I was planning to implement StackWise Virtual Configuration between two or three switches, can you please provide a sample configuration of how this would look and what the physical connectivity between the switches should be.
3. What would be the potential Cisco StackWise Virtual throughput difference between using Hundred GigE, Forty Gigabit Ethernet or Twenty Five GigE interface for SVL links between switches?
4. Is there a future plan to introduce Graceful Insertion and Removal for the C9500-32C, C9500-32QC, C9500-48Y4C, and C9500-24Y4C models of the Cisco Catalyst 9500 Series Switches?
Thank you.
We recommend checking out our Cisco Switching Community: community.cisco.com/t5/switching/bd-p/6016-discussions-lan-switching-routing, where you can connect with peers and switching experts who can answer your technical questions. Thanks!
Hi, is DAC/AOC cable supported, or only SFP transcever is supported for SVL/DAD
AOC is also supported
With Fuji release, the command int Te1/0/X -> stackwise-virtual dual-active-detection doesn't work anymore.
cannot use L3 Multi-chassis etherchannel?
Should these commands be ran on the initial setup of a switch, or once configuration is completed on a switch?
These commands are run once you configured your switches.
Do you need to configure SVL, Dual Active Detection and MCE on different Ports or can this be 2x40GB uplinks?
Mark van Veelen its recommended to use higher speed links for VSL in a redundant fashion as it’s a fallback in case you need to have data plane traffic traverse it. The purpose of the dual active detection is about detecting conflicts in configuration and state of the two chassis. It doesn’t require much bandwidth at all, even a 1Gbps link will do for it, again deploying this in a redundant format is recommended. So in summary use 2x10Gbps or 2x40Gbps for the VSL and 2x1Gbps or 2x10Gbps for dual active detection. HTH
then it means it at least to have 4 links recommended?
Each type of link should be redundant, so yes.
For the "channel-group", don't you still have to configure the "port-channel" (as a truck, - or - no switchport with an IP)?
from the text book approach, what ever is configured on the physical interfaces has to match the channel that you grouped them into, if you have mismatches between the physical and the Po then you will run into issues, what i have seen on the field on the latest OS, is changes made to the Po automatically get pushed to the physical interfaces, but if you change something on the physical interface then the interface will exit the Po membership.
In a regular stackwise setup ive connected switches like A->B->C->D->A so that a cable/switch could fail in the middle and the stack still has full communication. (A and D would the uplinks to the core) Does this work with virtual stackwise? Would you need a dual active detection link in this case?
Yes, it is recommended to have DAD links in SVL setup because you are using front panel ports with regular cabling for stacking switches compared to back stacking which uses dedicated ports with dedicated cables in a ring fashion.
Thank you for the sub-titles
This is the same as old VSS but with different name and just a bit changes in commands
config stackwise(1,2,3 step config) domain id both switch or just single switch?
both! the stack wise config has to match on both, and then you can establish who is active and who is standby later on
several links in a SVL is recommended but not illustrated in the video or comments (or anywhere it seems in fact).
Can you configure several links in a SVL with an interface range command ? as in :
Device(config)#interface range FortyGigabitEthernet1/0/1
,FortyGigabitEthernet1/0/2
Device(config-if)#stackwise-virtual link 1
or Do yo have to configure several SVL ID numbers like in :
Device(config)#interface range FortyGigabitEthernet1/0/1
Device(config-if)#stackwise-virtual link 1
Device(config-if)#interface range FortyGigabitEthernet1/0/2
Device(config-if)#stackwise-virtual link 2
It is too bad since it is what is recommended it is not shown as an example somewhere
It seems like the latter method is the way to go, looking at the command reference document
can we configure VSL and Dual-Active-Detection both on single link on 9407 R Chessis switchs.(bandwidth of link is 10 gig).
if yes, then would it work properly if one switch goes down .
please reply me as soon as posible.
Do not use the same port for StackWise Virtual link and dual-active detection link
Excellent!
Fails tech video rule 101 - No Music.
Please remove the background music
Great
With you and you can call
Please, Please, Please - Remove background music!
WHY?!? Why does this have annoying music running at the same volume as the speaker? I have to try to hear & understand his accent while it's being masked by that infernal music. Again, Why? I had to kill the volume and just go with the subtitles (I hope they're right). Another d@m^ed video made strictly in the Marketing Department! Very tempted to just down vote...