Thank you for this helpful video. I just got a question: Would it not work, if you configure both the Switchs with identical port-channel & virtual link number? Or they must have different port-channel and virtual link numbers?
thanks for the tutorial. i have a question, if before the convert to vss any configuration from core a & b, after convert vss core a & b, will the configuration before lost or not?
Thanks for the video. Question though; was the interface level trunk commands not needed? What type of encapsulation is the VSL using? Is it something new that Cisco came up with? I would suspect that it's neither ISL nor DOT1Q.
In terms of config, once you have converted to VSS you no longer need to worry about the physical switches. The active switch, whichever that happens to be at the time, provides the console/terminal/management interface for the virtual switch, and all configuration takes place through there. For example, if you ssh into an IP address assigned to a VLAN interface on the VSS, it is the active switch that responds and provides the terminal. Under everyday circumstances you don't really care about that, but the main thing is that you are now configuring the entire *virtual* switch, not either of the physical switches. You may have noticed the console message 'This command will convert all interface names to naming convention "interface-type switch-number/slot/port"' when TK issues the "switch convert mode virtual" command. This is because you now configure the physical interfaces for both switches through a single console, and you therefore need a way to reference those interfaces uniquely across the entire virtual switch. The same goes for any other commands, including adding a routing process. There is only one control-plane for the virtual switch, so when you configure a routing protocol, you only do it once and the VSS takes care of the complexity of distributing the config and data-plane operations across the physical switches for you (thanks Cisco!) Basically, once you correctly configure VSS (simply follow this nice video :-) ) you have one big switch instead of two (or more) smaller ones. One control-plane, one data-plane, one management-plane. By the way, nice video TK, thanks a lot :-)
Hard to view even at 1080P. In future.... Use different color combo for telnet session and larger fonts. Look to ine.com to see how to present it video. Good info though, thanks.
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
Nicely done, short, to the point, exactly what I was looking for.
Short, sweet, and straight to the point. Excellent. Thanks!
After seeing this video only I came to know about VSS configurations it very easy and simple Thanks a lot..
Great Video, short but very practical and objective.
thank you its nice illustration
thank ou so mush ,your way of explaining is such great
Used this for my 4500x switches also. Thank you!
thanks a lot. may the peace,mercy and blessings of God be on u always
Thank you for this helpful video. I just got a question: Would it not work, if you configure both the Switchs with identical port-channel & virtual link number? Or they must have different port-channel and virtual link numbers?
Wow.. That was superb..
Very short and good video.. Thanks
nice share video about vpc
Thanks for the video..Stay blessed
Great vid. Thank you for sharing your knowledge.
thanks for the tutorial.
i have a question, if before the convert to vss any configuration from core a & b, after convert vss core a & b, will the configuration before lost or not?
Thanks for the video. Question though; was the interface level trunk commands not needed? What type of encapsulation is the VSL using? Is it something new that Cisco came up with? I would suspect that it's neither ISL nor DOT1Q.
great video, thanks for sharing.
Perfect example, Thanks man!
Thank you. Very informative!!
Which command is to check the redundancy is working or not
further you need to explain while you are doing configuration what are you doing.. just a brotherly advice.. good effort.. cheerz..
Thanks for configuration of port-channel. What about 'Fast Hello' & 'BFD' links
super - simple - useful
very straight, thanks for the video
what about redundancy mode ? do we need to configure sso or rpr between supervisores of the VSS
great video
Does this wipe out the current config when you do this?
Many thanks for the video.
Very useful
Thanks
Thanks , if i want add interface vlan or routing should i add on both switch or just the active ?
In terms of config, once you have converted to VSS you no longer need to worry about the physical switches. The active switch, whichever that happens to be at the time, provides the console/terminal/management interface for the virtual switch, and all configuration takes place through there. For example, if you ssh into an IP address assigned to a VLAN interface on the VSS, it is the active switch that responds and provides the terminal. Under everyday circumstances you don't really care about that, but the main thing is that you are now configuring the entire *virtual* switch, not either of the physical switches.
You may have noticed the console message 'This command will convert all interface names to naming convention "interface-type switch-number/slot/port"' when TK issues the "switch convert mode virtual" command. This is because you now configure the physical interfaces for both switches through a single console, and you therefore need a way to reference those interfaces uniquely across the entire virtual switch. The same goes for any other commands, including adding a routing process. There is only one control-plane for the virtual switch, so when you configure a routing protocol, you only do it once and the VSS takes care of the complexity of distributing the config and data-plane operations across the physical switches for you (thanks Cisco!)
Basically, once you correctly configure VSS (simply follow this nice video :-) ) you have one big switch instead of two (or more) smaller ones. One control-plane, one data-plane, one management-plane.
By the way, nice video TK, thanks a lot :-)
very good ..
nice understanding....
Nice
hi, is that config made in real equipment or any emulator system?
How it worked with different Port Channel numbers configuration?
Came across this video, port channels don't need to match
can we use VSS in eve-ng/ GNS3
thanks
how we can upgrade their IOS ?
awesome!!!
thanks a lot
U might wanna show 1 screen at one time..I can't read anything on my cell
cant see anything on video...
Hard to view even at 1080P.
In future....
Use different color combo for telnet session and larger fonts.
Look to ine.com to see how to present it video.
Good info though, thanks.
Incredibly boring. If this doesn't turn people off from networking nothing will.
Thanks a lot... Amazingly done!
very helpful thanks a lot .