ENCOR - Enterprise Network Design

[@markdunn756]

This series is truly a diamond in the rough. So many of other sources are just "Exam topic --- xyz --- ok now you know that specific topic." To just have a topic then a 1hour like real "class" on it with lots of real world approaches is something you just dont find. I wish I could double thumbs up.

[@shamax2201]

Loved the STP failure storey, and what you mentioned about having to stand your ground that you did the right thing, and repeating the exact same change (plugging the cable to the same switch and same port) after hours and proving that you did the right thing the first place - I can relate to this. I didn't enjoy the PIR meetings with the client and my own company, as no one believes that you did the right things.. they believe somehow you made a mistake that you didn't want to admit... Anyways. Thanks for these lessons. Very nicely done.

[@DD-mr2tk]

Through 20 min now; very informative. Resuming whenever I have free time.

[@expressionofwill5307]

That few minutes at the end about SDA is the best I have heard a SD Fabric overlay explained anywhere

[@rembautimes8808]

Absolutely loved the video and I was glued to it from halfway across the world! There was one point which contrasted technical expertise vs communication skills. Realistically, the world is such that those who are more adept at communicating who can speak the language of business usually progress at the expense of those who are technically expert. But speaking from a risk management perspective, I would 100% rather have the network guy in my company be the best technical expert, whose word is law, rather than someone who goes with the flow. And in a highly regulated environment like financial services, regulators have the back of the technical expert. So if there was a meeting and a technical expert says , “no you need to do this in A and B and C”, and he has the necessary street credibility, very few committee members will dare overrule him. And he will also have the backing of risk, who has a powerful voice.

[@mattmcg3760]

Mr Kish - Applying theory to real world scenarios like a boss!

[@razitouch]

A challenging topic ...that most network engineers come across during their career at some point. Great content and many thanks for sharing your views and experience

[@eugenealejandro8627]

This guy is my new all-time fave Guru!!!

[@biz20072008]

I know you Jeff from being a cbt nuggets subscriber for 3 years now and you are the best. This is a great complement to those courses, seriously. Thank you!

[@ochanlee4414]

Wow! How I wish I discovered you earlier Jeff Kish! I felt like a Network guru after this video. All the buzz words like VXLAN, SDX, blah-blah suddenly sank in as though I was literally eating yellow bananas as opposed to roasted corns. Thank you and keep the great videos flowing in!

[@samjones4327]

Awesome, Awesome, Awesome video/tutorial! I am a Cisco networking academy student studying for my CCNA level cert and your explanation made total sense to me. Thank you sir!

[@landreewilliams]

You CAN actually span VLANs across multiple L3 access switches in the event that HR decided to buy that application that requires it. I do it everyday with no hiccups, although it does take a little extra backend configuration on the aggregation layer, but nothing that should stop you from running L3 to the access. I also love L3 access for ease of matching IP to MAC in the event of some troubleshooting. I'd be happy to share config examples of this type of set up to help others. Also, I like your videos. Very good.

[@KishSquared]

What technology are you using to span across L3 boundaries? I'd love to know how you're doing it!

[@landreewilliams]

@@KishSquared Absolutely. Let me see if I can get something for you and post some screenshots of example configs on imgur and will post the link in the comments.

[@Lucas-md8gg]

These 1h+ videos are awesome!

[@alejandrosisco2100]

you are the best explaining network architctures out there for sure!! thank you very much!

[@adrianmxmx]

Thank you for your time. I know SD-WAN real well and look forward to DNA SDA!!

[@adrianmxmx]

I have been working as a principal engineer for the top two companies for many years and direct colleagues to your site for mainly real world design understanding. Trade-offs (Decision points), Dependencies (one or many components requires to function), constraints etc. For design, looking at flexibility, scalability, modularity, repeatability with a small brush of choke points to curb setbacks bleeding into another plane. I would love to see you have a video on IP Design given that it will reflect the flow as well as boundaries to not just throw out to the ether. Huge FAN. Keep it up. Most everyone can learn the syntax, yet your channel brings to the table knowledge transfers for an entire footprint I see lacking within the space.

[@mathiasastrom5228]

im in last day before CCNP 2 exam, and your vides helps me a bunch! wished i found it earlier :) thx alot and good job! you help us alot!

[@AB-fj5wi]

did u pass?

[@ajitnagarkar8640]

That was Spot on considering the real world scenarios and reducing only the bookish knowledge.

[@donedeal51]

Great videos! Your channel is definitely going to blow up. There's not very many making videos on real world enterprise networking.

[@HinSela]

Thanks you for this video who bring our rookie engineer to the real world and not only for exam.. well done

[@philip1760]

thanks alot jeff . always making complex things easy to grasp with some real-world stories

[@Vision06]

This content is highly appreciated, thank you so much KishSquared!

[@realstevelknievel]

That's some great content and advice! Hopefully there'll be a new video soon. Keep up the good work!

[@alexandruchiriac7212]

A very usefull information for a networking engineer mind set, thanks!

[@kappi4882]

Thank you! Very well explained.

[@minnalavlog4533]

Really a helpful video, waiting for next

[@OoOAndrucoOoO]

I loved how you explained this and how enjoyable it was, new sub bro!, im gonna check your other videos, keep the good work!.

[@rochuolmos]

a massive thanks! you're a savor

[@thealbapone]

Thank you for this very interesting analyse about L2 versus L3 access implementation. Congratulation for your videos they are really good!!!

[@suhaybmaxamed602]

thank you jeff it's very help full

[@aahamdam34]

Thank you soo much but Your playlist videos must have Sequence like 001, 002 and so on ! otherwise its hard for us follow your videos ! and is this gonna be a complete CCNP course or just highlights of it ???

[@KishSquared]

Thanks for the comment, I went ahead and re-organized the playlist so it's in order of domain topics. I hope that helps! While it's not intended to become a complete CCNP course, we'll just take it one session at a time and see how far we get :)

[@jalalhaider83]

25:33 when you talk about collapsing, what do you mean by that when you say core/distribution collapse to one what does that mean just a distribution switch only or what? I mean core is basically routing, which layer 3 switch aka distribution can also do? Looking forward to hear from you, thanks

[@KishSquared]

Distribution and Core essentially equate to different functions, where Distribution is SVIs and L2 connection to Access, while Core is L3 connection to other network locations. When you collapse to one, you have a single switch pair doing all of the above. I hope that helps!

[@jcoeder]

Love you videos. What do you use for the chalkboard. What hardware and software?

[@HinSela]

I saw u talking about L3 on access tier. How could the L3 working without L2 … I’m confuse now.

[@kauldeepak1]

Great session..do you have any session on software defined DC LAN design..how to size an ACI architecture with spine and leaf switching. Thanks

[@paulodecimo5436]

In the Campus design, how connections between the Distribution switches in each building and the Core switches (are they switches or routers?) work? By routed interfaces? L3 Etherchannels?

[@KishSquared]

@@paulodecimo5436 The links will be L3 back to the core (usually these are multilayer switches). You can use Etherchannels but there isn't really an advantage to using them over flow-based ECMP. Hope that helps!

[@paulodecimo5436]

@@KishSquared Hi, helped a lot, thank you. Please keep going with this study group. At the CBT nuggets classes you're kinda at the job and here its like you're just chilling with your boys talking about networking 🤣🤣🤣

[@jogandomais]

Awesome content, thank you so much!

[@rubenjaldinsalvatierra2535]

Dear @kishSquared one question to the DC Block, i´m capable to use my Fabri´s Interconnects to connect my SAN , i mean i Know we have a MDS Product, but can i use my pair of FI to reach the old and traditional SAN, and what are the real differences in real life to do or no do that... thanks a lot , Sensei !!

[@rubenjaldinsalvatierra2535]

Or even with the Nexus Switches with UP port´s , and not use the F.I.

[@KishSquared]

For traditional FC SANs it makes a lot of sense to connect your FIs directly to the FC switches. Certainly you could extend FCOE to the upstream Nexus as well if you have reason to do so. If using native FC, you would connect the FIs to the MDS switches, and then the storage would also connect to the MDS. This way you have end-to-end FC connectivity all the way down to your servers via the UCS FCOE connections. I've done this plenty of times in my designs and implementations and it works great. I hope this helps!

[@codeforsteamchannel1761]

Great video

[@YLprime]

I don’t understand why we will need FHRP on L3 access switch. Everyone wants to explain? Thanks

[@KishSquared]

Usually there are still multiple access layer switches per closet in an L3 Access design. Since the gateway address now lives at this layer, you would want redundancy among the access switches. Granted, if you are isolating a set of hosts to a single access switch/chassis/stack, then there's no need for an FHRP since it's a single device. I hope this helps!

[@YLprime]

Interesting! thanks!

[@habeebayesh3754]

Hi Jeff, what about spine and leaf network Design ? thanks

[@KishSquared]

Spine and Leaf is primarily a data center architecture that is enabled by VXLAN and/or software-defined infrastructures. So certainly something to consider while building DC networks!

[@osamashawky7853]

Many thanks for ur video and ur efforts ,please help i need to ask you for top urgent case with me , what about performance of tp link enterprise model for school with below network for school whats about stability with poe Access point Access point controller Control ssid I will make 4 ssid in all school with vlan Vlan stable of not Poe is good or not Managed switches .be 32 switches poe 24 and 48 Core switches All work is nvr with 600 camera Systems & servers Cables will be cate 6a and fiber 100 classes User will be 6000 user Firewall will be sophos Recommend or not Many thanks in advance ☺️ 🙏 If u recommend this Which model number will be good and compatability with this operation Swtich and Access point

[@changwang7596]

That shiny head

[@saikumarnatarajan5757]

Can u please tell more clearly what is collapsing 2 layers actually mean ?

[@KishSquared]

You bet! Collapsing two layers means that we're combining their responsibilities onto a single set of physical hardware. So collapsing Dist and Access means that a switch would connect users (Access responsibility) as well as provide SVIs and FHRPs (Dist responsibilities). Generally you can collapse any number of layers so long as they're logically adjacent to one another - e.g. you can't really collapse Core directly into Access, but you could collapse Core-Dist-Access together. I hope that helps clarify things!