ENCOR - Switching Mechanisms
Вставка
- Опубліковано 11 вер 2024
- In this video, we explore Switching Mechanisms as part of the ENCOR blueprint. This includes concepts such as CAM, TCAM, RIB, CEF, and FIB!
UA-cam Playlists from Jeff Kish
▶ ENCOR Study Group: • ENCOR Study Group
▶ CCNA Study Group: • CCNA Study Group
💻 Jeff's ENCOR content on CBT Nuggets: learn.gg/encor-...
💻 All of Jeff's content on CBT Nuggets: learn.gg/jeff-...
#ccnp #encor #ciscocert
22:55 that does look like trying to play "gotcha" in interview questions. In the older days technical flex was super competitive, not so much these days. Thanks for this training.
Thank you so much for this!! Been reading the CCNP ENCOR Cisco Press book and trying to wrap my head around this topic, and with your explanation, I understand now! Looking forward to more of your study sessions live so I can join!
Awesome video once again! Thank you
Can it be that the 9600 is centralized forwarding
Brilliant content.... You simplified this content so well.. no words .. hat's off to you
Nice and simple.
Thank you very much for the informative session 🙏
Thank you for this explicit explanation. Much grateful if you could provide a lab demo. I've the lab in GNS3 and CML. I'm a bit confused. With CEF enabled globally on a router., I turn off CEF on one of its interface where packets are received with the command no ip route-cache cef. The debug output shows the packet is switched via FIB which is used by CEF. So turning off CEF on the inbound interface does not change anything as the packet is still being switched via FIB. Thank you for your reply
But how RAM and CAM are completely the opposite as you stated at the beginning?
Hey Jeff,
Quick question, is Adjency table still used in CEF?
Hello Jeff !! You know that in the ucs manager you can see your fabric interconnects connected both up the network and down the servers and between them you see most of the time or almost always a connection that I imagine is for the configuration replication between them, my question is I was reviewing the environment in ucs manager of a client and I see that the link between the 2 fabric interconnects is in red, that is, it seems that there is no connection between them, this happens due to some type of license in the equipment or something like that, how can I start the corresponding tsoot
Not relevant to ENCORE. Just a general question, when windows PCs connects to a Hub, even today, it is like windows is going to detect (whatever logic they use) that they are connected to a Hub and slowly they switch back to the older CSMA/CD way of doing things? Is that correct? Its very interesting then..Do you know any book that talk about this specifically?
There's actually no adjustment that needs to be made. Ethernet NICs must abide by CSMA/CD even if they're the only device on a collision domain, because we never know for sure that another talker won't appear. There is no way for a NIC to detect that it's on a full-duplex link. Fortunately, CSMA/CD doesn't affect communications until a collision occurs, which would never happen on full-duplex, so there's no real downside to this.
I would expect any CCNA book to discuss this in detail!
@@KishSquared thanks Jeff