As a young network engineer desperate to keep up with far experienced colleagues and rapid new technologies, I can only say thank you and keep up the good work. Visual explanatory > abstract thinking
Same here! This video was kind of a life saver. Nexus Switches never got taught in our school and there's no way you can practice them on Packet Tracer. Really good video ! Thanks
Damn, pardon my french, but I think I found a hidden gem among thousands of networking channels on YT. I've seen your vxlan series and now this one, 100% perfection. From a Net Admin to another, many thanks.
7:49 the menacing ransom note style omg thats brilliant. I am definitely not forgetting these lessons the way you're cleverly framing and demonstrating them. nicely done!
Glad you found it useful. Thanks for the feedback. I don't think I'm in a good position to cover VDC or OTV at this time. I don't have enough experience with them to do them justice. Maybe one day :)
great job, one thing, that scratching sound to simulate the writing, was driving me nuts, I couldn't complete the video, but the content and the speed is perfect, thanks
Appreciate your efforts. Your videos are short, but covers all the major components of the topic; nevertheless they are far easier to understand than many other commercial stuffs out there.
@12:34 Can I please be informed why there would be no issues if keep-alive link fails but peer link is fine? Do we mean to say that peer link will indicate to the two switches that another switch is alive? If yes, what is the use of having the keep-alive link at all if the peer link already does this job? Am i missing something?
I am new to vPC, thanks to your well detailed presented Video, i am well aware of the basics now, thank you.: One Question, the keepalive or the peer link only monitors the link between the peers or the peer switches themselves, but not the member link of each vPC peer switches. In scenario where the peer link goes down, as you mentioned, the secondary switch disable the member port, but WHAT IF the member port of the primary switch goes down too, Now what, how will the secondary switch know of that. 2nd Scenario, in case where 1st peer link then the keep alive link goes down, the secondary switch will disable the member port, bot for how long, what if the primary switch goes down too later, how will the secondary switch know. will this need a admin intervention too or is there a workaround designed for same.
As I understand it, in scenario 1, the secondary will shut down the member ports as you say. If one of the member ports then goes down on the primary, the secondary won't do anything about it. It keeps its ports down until the peer-link is fixed. It does this for (1) loop prevention, and (2) because it has no way of knowing about the failure on the primary (as the peer-link is down)
For your second scenario... If the peer and keep alive links are down, the secondary switch cannot know the state of the primary. There are no links the switches can use to communicate this information. This would be a rare scenario, but it is definitely where we need admin intervention, perhaps to manually swap the roles, or ideally, fix the peer-link and keepalive
I didn't understand one thing and will appreciate if someone explain it to me. In 12:10 case when primary switch turns off and in 12:50 when keep alive connection breaks I thought for Secondary switch this cases are the same and result will be also same
Your visuals really help, thanks for the video! When you see a port-channel between peers in some topologies, is this what contains the keep alive and peer link? Or are they meant to be configured separately?
Good question! They need to be physically separate. A layer2 link (ideally a port channel with trunking) for the peer link, and a routed link as the keep alive They need to be separate, as a failure in one shouldn’t affect the other
Probably not for a while at least. I don’t feel that I know these technologies well enough at this time. Possibly some time in the future, but it wouldn’t be soon, sorry.
Do you mean adding HSRP to the switches that are also on vPC? This works quite well. I haven't done it in a while, but from memory it's just regular HSRP config
@@NetworkDirection Thank you for replying. I wish I could share the topology diagram. Current topology is 2 Catalyst SW configure with HSRP and are in Active/Standby with VIP addresses as default gateways for multiple VLANs. Between the Catalyst there is a L2 trunk connection. And what I meant was to connect the newly configured vPC domain to the 2 Catalyst switches. Active Catalyst connected to vPC peer1 and Standby Catalyst connected to vPC peer2. Will the above work or do I have to configure additional settings? Thank you in advance.
Is there any way for the switch to deny traffic going out across the peer-link if it's destined to only go out of port-member's only? Seems like you're just making extra work for the switch to process the traffic and send it out of the peer-link only for it to be dropped
As a young network engineer desperate to keep up with far experienced colleagues and rapid new technologies, I can only say thank you and keep up the good work.
Visual explanatory > abstract thinking
You're very welcome. It's good to hear that the videos are working :)
Same here! This video was kind of a life saver. Nexus Switches never got taught in our school and there's no way you can practice them on Packet Tracer. Really good video ! Thanks
Damn, pardon my french, but I think I found a hidden gem among thousands of networking channels on YT. I've seen your vxlan series and now this one, 100% perfection. From a Net Admin to another, many thanks.
You're welcome! Glad to share the experience around
where is the french?
7:49 the menacing ransom note style omg thats brilliant. I am definitely not forgetting these lessons the way you're cleverly framing and demonstrating them. nicely done!
Great approach to the subject - if someone is a visual learner, all it takes is watching your video twice and it gets into the blood! Cheers mate!
so good to hear that you like the videos, thanks!
One of the best explanation I have come across. Complex topic explained so clearly. Like the animation used. Thank you for this video :)
THis kind of video for VDC and OTV will be a boon to humanity. You are awesome thanks a lot for breaking down in the best way... kudos..
Glad you found it useful.
Thanks for the feedback. I don't think I'm in a good position to cover VDC or OTV at this time. I don't have enough experience with them to do them justice. Maybe one day :)
Sound effects at 12:13 made me lol. Another good explainer!
hahaha! I need to do more things like that 😆
great job, one thing, that scratching sound to simulate the writing, was driving me nuts, I couldn't complete the video, but the content and the speed is perfect, thanks
Yeah, I've since stopped using it
You videos are so amazingly professional I feel like deleting any videos I ever put up. Great job
Just needed to do a quick review on some technologies all I can say is thank you, your video is top notch 👍👍👍
Thank you very much!
Man this is a great explanation. You made me understand vpc in an clear way. Kudos
A clear explanation was the goal, so I'm glad it worked out :)
As I mentioned in the video, let me know if you're interested in routing over vPC
Network Direction Yes please.
Thanks for the feedback! I'm a bit slow at creating videos, but I'll get it done :)
Yes please.
Routing over vPC video is here:
th-cam.com/video/KPsnI6h1RIs/w-d-xo.html
Wonderful explanation with all important concepts and scenarios in short video
Awesome explanation of how VPC works!
I am new to vPC, Well Explained!!
Appreciate your efforts. Your videos are short, but covers all the major components of the topic; nevertheless they are far easier to understand than many other commercial stuffs out there.
Thanks Prashant,
I find shorter is better in many cases.
outstanding video. better than some other paid video series! you just got another subscriber!
Clear explanation , thanks!!
Thanks for watching
Very useful.
Although this video was made over 4 years ago, it is still the best video explain vPC.
Thanks!
Simple and quick explanation.
Explained very simple and clear
you make learning very fun. thanks
Excellent explanation using animation, simple and easy to understand and. Appreciate!!
Fantastic explanation in simple manner. Thanks.
Thanks Rajib, I appreciate the comment
Wow brief still well organized explanation. Thank you...
Thanks... I plan each video out before starting, which helps a lot with organization
I Loved the way you described vPC . really appreciate your hard work !!
I really appreciate your comment! Thanks Azhar!
you made this content is very explicable , thanks to you .!
Glad to hear that!
Awesome and simple explanation really likes the way you explain the concept ,keep up good work
Thanks a ton
I love all of your videos, clear and right to the point. I'll stick by for eternity.
Thank you so much :)
Awesome, thank you!
Excellent explanation and animations, really helps this video to understand the basics of vPC. Thanks!!
Thanks! Glad to help!
Awesome video about VPC
@12:34 Can I please be informed why there would be no issues if keep-alive link fails but peer link is fine? Do we mean to say that peer link will indicate to the two switches that another switch is alive? If yes, what is the use of having the keep-alive link at all if the peer link already does this job? Am i missing something?
Really Nice Explanation !!!
Thanks!
Loved the explanation great work great review had not done it in years thank you Im interviewing again and I had same question for fail over
Thank you for establishing such an easy understanding.
Excellent presentation
you are very methodical, thank you for this simple explain
Fantastic video! I understand the concepts so much better now!
Nice video, it's really informative with excellent animations.
Thanks Andrew 😎
Thank eu so much all the part of vpc was great explained....waiting to see more videos on DC..
Thanks!
I have a video on Nexus tips coming soon.
awesome man keep up the work got clear insight on vPC
Thanks Sandeep, I'll try to keep it up.
My current project is a series on how VxLAN works, including configuration on Nexus
Amazing Very short and precise video.
very enterteined!!dvery good and excellent well done please do more videos are very very good
That was very well explained thank you.
thank you!
Yep great video, thanks for the detail.
You're welcome!
Thank you for Sharing information. Great explanation!
Thanks Chetan!
made it so clear , thanks buddy
Glad it helped!
Excellent presentation of Video .You make the concept so easy to understand. Yes will be interested in routing over vPC
Thanks Shabbir
Good news! I've already done the routing over vPC video. Here it is:
th-cam.com/video/KPsnI6h1RIs/w-d-xo.html
it's really informative with excellent animations.
Thankyou, I'm glad you like it!
Really great explanation and examples which u share it’s awesome
Thanks! You're welcome!
Great explanation and presentation thank you sir
you've got new subscriber!
awesome explanation !!
Thanks for subscribing :)
Glad you liked it
I really liked the way you explained. Thanks for the awesome video.
Excellent Explanation
easily understandable. Thanks for the video.
thanks for the informative video
very clear and to the point. much appreciated
You're welcome!
Thanks for sharing a nice video.
I have one question.
If configure VPC, usually only the VPC primary switch will receive/forward frames??
No, as I understand it, they both can forward frames
very easy to understand. Thank you very much.
Glad you like it, thanks!
Congrats, very good explanation.
Fantastic lecture👌🏽, thank you.
you're welcome, thanks for watching
Thanks my dude! tomorrow i will be configuring one of this with my team and the Cisco docs f*cking sucks lol. love from Venezuela!
Thanks! Glad to help!
Great explanation
Glad you think so!
Excellent presentation 👍
Thank you
@2:30 what are examples for control plane traffic in this case?
Great video... love the animation
Just amazing! Subscribed!
Thanks Pav!
I am new to vPC, thanks to your well detailed presented Video, i am well aware of the basics now, thank you.:
One Question, the keepalive or the peer link only monitors the link between the peers or the peer switches themselves, but not the member link of each vPC peer switches.
In scenario where the peer link goes down, as you mentioned, the secondary switch disable the member port, but WHAT IF the member port of the primary switch goes down too, Now what, how will the secondary switch know of that.
2nd Scenario, in case where 1st peer link then the keep alive link goes down, the secondary switch will disable the member port, bot for how long, what if the primary switch goes down too later, how will the secondary switch know. will this need a admin intervention too or is there a workaround designed for same.
As I understand it, in scenario 1, the secondary will shut down the member ports as you say. If one of the member ports then goes down on the primary, the secondary won't do anything about it. It keeps its ports down until the peer-link is fixed. It does this for (1) loop prevention, and (2) because it has no way of knowing about the failure on the primary (as the peer-link is down)
For your second scenario...
If the peer and keep alive links are down, the secondary switch cannot know the state of the primary. There are no links the switches can use to communicate this information.
This would be a rare scenario, but it is definitely where we need admin intervention, perhaps to manually swap the roles, or ideally, fix the peer-link and keepalive
Absolutely excellent video! Very informative. thanks.
Glad you like it, thanks
Excellent video. Thank you for sharing.
You're welcome, glad you like it!
Great explanation, what software do you use for your presentation?
I use a few different things. Fusion for the 3d parts, powerpoint for the 2d animations, and Shotcut for timeline editing
Excellent presentation 👍👍👍👍👍👍
Thanks Khan!
Superb and best explanation...
Thanks!
This video is amazing
Thanks, glad you like it!
you are the number one! thanks!
Thanks for your support! I’m glad you like my channel.
I didn't understand one thing and will appreciate if someone explain it to me. In 12:10 case when primary switch turns off and in 12:50 when keep alive connection breaks I thought for Secondary switch this cases are the same and result will be also same
Got cleared about VPC.
Do you have any video about how VPC works with MAC pinning
Clear explanation. Thanks.
You're welcome!
Your visuals really help, thanks for the video! When you see a port-channel between peers in some topologies, is this what contains the keep alive and peer link? Or are they meant to be configured separately?
Good question!
They need to be physically separate.
A layer2 link (ideally a port channel with trunking) for the peer link, and a routed link as the keep alive
They need to be separate, as a failure in one shouldn’t affect the other
Thanks for your great explanation. could you please have video about vpc with HSRP.
That's a good idea.
For now, there is an article I wrote on this topic that you may like:
networkdirection.net/vPC+with+HSRP%2C+VRRP
Great explanation, very easy to understand.
Can you make videos for >> VSS, VRF, OTV?
Thanks Ken!
VRF videos are in production now. They’ll be a fast paced 4-part series
Thats awesome, will you also make VSS and OTV?
Probably not for a while at least.
I don’t feel that I know these technologies well enough at this time.
Possibly some time in the future, but it wouldn’t be soon, sorry.
Its okay no worries, thx a lot anyways, keep up the good work.
To connect the vPC to L3 switches (hsrp) for VLAN routing, are extra configuration required?
Do you mean adding HSRP to the switches that are also on vPC?
This works quite well. I haven't done it in a while, but from memory it's just regular HSRP config
@@NetworkDirection Thank you for replying.
I wish I could share the topology diagram.
Current topology is 2 Catalyst SW configure with HSRP and are in Active/Standby with VIP addresses as default gateways for multiple VLANs.
Between the Catalyst there is a L2 trunk connection.
And what I meant was to connect the newly configured vPC domain to the 2 Catalyst switches.
Active Catalyst connected to vPC peer1 and Standby Catalyst connected to vPC peer2.
Will the above work or do I have to configure additional settings?
Thank you in advance.
@@b0ys0l09 I may have misunderstood, but I didn't think vPC was available on the Catalyst platform. Only the Nexus?
@@NetworkDirection the vPC peers both are nexus switches and the plan was to connect them to the Active/Standby catalyst switches.
@@b0ys0l09 Yeah, that should be fine. You will probably find increased traffic on the peer link.
Great explanation sir, thankyou!
Nice content and Very nice explanation ..
Keep up the good work .
Excellent instructions
thank you
thanks so simple explain complex topic
really good explanation
Glad it helped!
Great Video!
Thanks Rohit, I'm glad you like the channel!
Excellent 🙏
Thanks, it's very understandable
Man you a great a explaining things. Thank you!
Love the animation they are awesome
thanks!
Best Presentation.
That means a lot, thanks!
Great job !!
great job! Thank you!
You're welcome!
So the keep alive link doesn't need to be multiple links, like in port/etherchannel?
Excelente video, explicacion y animacion que deja claro el concepto. Gracias
nice explaination
Big thanks form Russia!
Is there any way for the switch to deny traffic going out across the peer-link if it's destined to only go out of port-member's only? Seems like you're just making extra work for the switch to process the traffic and send it out of the peer-link only for it to be dropped
I think that's handled in the ASIC, and may be platform specific.
So as far as I'm aware, there's nothing you can configure
New sub! Am here coz someone dared to answer this topic. Thanks 😊
Thanks! It was a tricky one to cover, so I'm glad it's helpful