Відео

Hey, good video, just wondering, is this serious solely focused on Juniper or do you reference Cisco at all?

Thank you so much for this content!

crap, I was so excited for this video then found out it's for juniper, not nexus. Oh well, the steps are great and I think translate to Nexus on a high level. Thank you!

Crisp and to the point.....😊

thanks a lot for this super video. It should be useful to have another video with Campus Fabric Core-Distribution layout.

Thank you for this great video, I have a question, in case each port of the bridge has it's own VLANs configuration, does the MST in the BPDU be different from port to another ? And what happened if two ports have a common vlan ?

Excellent work you are doing. Thank you so much for making difficult concepts very easy to understand. I appreciate the level of detail and information in all your series. Keep it up.

Very thorough, I can't understand why so few views.

@Netcademy Dave a QQ. In VLAN Bundle service model with the scenario that we considered with Leaf 1 & 2. Where Leaf 2 does not have vlan 30. Upon receiving update messages from Leaf 1, Leaf 2 will import all the MAC Addresses into MAC VRF 1 even though Leaf 2 does not have vlan 30. If i am not wrong, one of the benefit with Route target in control plane is for granular MAC address import. Cant we just import only VLAN 10 & 20 end host mac address into MAC VRF 1 on leaf 2 by tweaking route target? Correct me if my understanding with route target is wrong. TIA advance. Really appreciate all your efforts for making this wonderful series of videos.

Thank you for the time and effort taken to teach us

@Netcademy Awesome explanation and wanted to confirm if my understanding aligns with your explanation. Here’s my summary of the role of Route Distinguisher (RD) and Route Target (RT) in a multi-tenant EVPN/VXLAN setup. Is this what you were trying to explain? Route Distinguisher (RD): The Route Distinguisher is used to uniquely identify routes across different VRFs on the same device, especially in scenarios where tenants might use overlapping IP address ranges. By appending an RD to each route, the router creates a unique route identifier in the global routing table. This allows a leaf switch to differentiate routes for different tenants even when the IP addresses overlap. When routes are advertised via BGP (typically from leaf to spine switches), the RD ensures that these overlapping routes appear unique to remote switches. However, the RD only serves to distinguish routes within the network and does not influence routing policies or tenant association on its own. Route Target (RT): The Route Target is used to control the import and export of routes between VRFs and ensure correct tenant association. On a leaf switch, an RT is associated with each VRF to tag and filter routes based on tenant requirements. For example, a route with an export RT on Leaf 1 can be imported into a matching VRF on Leaf 2 using an import RT (configured with the same value). This allows for proper route segregation between tenants and ensures that each tenant’s routes are imported only into the appropriate VRF across the network. Spine Switch Role: In a typical EVPN/VXLAN design, spine switches do not require VRFs. They maintain all routing information in a single, global routing table and distinguish overlapping tenant routes using the RD. The RT then plays a critical role on the leaf switches to ensure that the advertised routes are correctly associated with the corresponding VRFs when received from the spines. When a spine switch advertises routes received from one leaf to another, it includes the RD, preserving route uniqueness across tenants, and the remote leaf’s RT configuration ensures these routes are correctly imported into the appropriate VRF based on tenant association. In summary: RD: Differentiates overlapping routes across VRFs in the global routing table but does not control tenant-specific routing. RT: Ensures routes are imported/exported to the correct VRF, maintaining tenant isolation. Spine: Operates with a global routing table, relying on RD and RT to maintain tenant route separation and correct VRF association on leaf switches.

Great video.Thanks for making it! If in case I need to connect the core switch directly to the Servers via ESI instead keeping access switch in between, how can i achive that- meaning how can i map the core switch port to the server in MIST. Could you please help to understand that.

hi, still waiting for day 1 video 😁

Really good video for the config however IMHO I feel the explanation is a touch confusing/could be more accurate. The Sub-ASs are referred to as "confederations" when in fact it should refer to the larger AS (and all the Sub-ASs inside it) as "the confederation".... The Oxford dictionary describes a confederation as "an organization which consists of a number of parties or groups united in an alliance or league. E.g. a confederation of trade unions" Take Canada as a further example...it is a confederation of provinces. Ontario (a province) is not itself a confederation but is part of the wider "Confederation of Canada". I only point this out to increase knowledge/understanding of the subject, not to pick a fight FYI

I posted earlier about help with inter vlan routing. I watched your whole series and figured it out! I really appreciate your series and your detailed explanation. Very good breakdown and teaching!

Great video. You’ve gained a subscriber

From an enterprise, we have configured more than 20 groups for different VLAN's. a QFX5100 contains 96 ports technically its possible to have more VRRP Groups

Where's part 5? Thank you

This video is amazing! I really hope you continue showcasing Juniper content because most other channels have great Cisco material, but not much on JUNIPER. It would be a fantastic addition to the community!

Superb content mate ! made my life easy on understanding all the concepts !

Hello, amazing video. Thank you for this! at 30:50 you mention the server wants to send BUM traffic which leaves from Leaf 3 and it reaches Leaf 1 and Leaf 2 but Leaf 2 drops the BUM traffic since it is not the DF then why does Leaf 1 accept the BUM traffic even though its not the DF

Good video thanks. To be honest I have lost it with respect to calling things Routers or Switches. In Data center spine leaf topology all the leafs run BGP, VXLAN/EVPN, VRFs etc... but we call them switches.

Hi David. I'm a bit confused about the configuration at the Leaf Switch*es level to accommodate a Server utilizing LACP across two disparate Leaf Switches. From your past lessons you'd mentioned ESI is needed; and we know the Leaf switches are NOT connected together *only to the Spines. Where can I locate that particular ESI configuration at the Leaf Switch layer to accommodate a Server's LACP bundle across two disparate Leaf Switches ?? Thanks ! Howard P.

At 20:00 for the case when all APs goes down at the same time and therefore the issue is not related to APs but to underlying switch that is connected to all APs. Shouldn't MIST-AI pinpoint that switch also that I am not able to communicate that switch that is connected to all APs and hence issue lies in that switch?

Your EVPN videos were very helpful to me. Grats on 3K. Good luck with JNCIE !

I started watching your videos recently and learned new things. Thanks and keep it up.

Hi David, I attribute you and your videos to one of the key reasons I passed my JNCIP-DC so thank you for all that you do

Keep.. Rocking

Lewis Kimberly Hall Dorothy Moore John

Really nice video with exact details that were of interest for me. Highly recommend this video to anyone interested in learning about LAG and LACP.

Great video!!

I think for PoE over fiber, you would need some kind of special cabling/transceivers as there really is no inherent way of sending power through fiber.

Tq

It always confuses me when you say mac-vrf is basically a switching table containing all MAC within a specific VLAN. In my head it's more like virtual L2 switch witch MAC table containing all addresses, of all vlans defined within that mac-vrf. Then ip-vrf is more like a virtual router with irb interfaces, not a collection of mac-vrfs

Thank you

Walker Deborah Martin Joseph Smith Michelle

Amazing explanation David, just two things that I believe would be a great addition to the video. First, how Cisco vs JunOS default VLAN traffic travels through a trunk? Tip: When Native VLAN is not configured on the JunOS side, problems exist with default VLAN traffic Second, while using IRB interfaces on the Switch, how do you enable connectivity between the Switch and the Router? The interface on the Switch needs to be a Trunk? an Access? Which VLANs would be assigned using the members command? How to put an IP on the interface Switch, if its a L2 interface?

Really solid video! Have been checking out a bit of your channel and I am really impressed with your work. Keep it up!

Can you do video on Mac VRF by giving cli configuration for each service type?

Awesome content, mate! Helps me a lot! Will watch all of the series now.

I like how you did these in steps and you listed the steps first, good video

Anderson Karen Lewis Frank Garcia Mark

This is really helpful. Thank you so much! Just curious - are type 4 LSAs from areas 3,4 and 5 also included in area 0 intra area LSA count of 100 or it would be additional three LSAs?

So, you changed the color of your background room.

Lots of content. Maybe break the videos down into smaller bite sized chunks. A lot of SE's just don't have the time 🙂. Great production.

Q1) When both vlans 10 and 20 are present on Leaf 1, do the IRB interfaces IRB.10 and IRB.20 belong to the same IP-VRF? Or do they have IP-VRFs of their own? Q2) How many route lookups does it take to route between IRB.10 and IRB.20 on Leaf 1, when the packet is to be tunneled over VNI 5020 to another leaf? The above questions pertain to Asymmetric routing!

Great video! It has been extremely helpful. Once you have this setup what is the best way to get out to the internet from a vxlan vlan?

Brown Brenda Davis Dorothy Garcia Carol

Thanks for the great explanation. I have a couple of questions here concerning the DF action mechanism. 1- you explained the case when the server 10.1.1.3 picks leaf 3 to send BUM traffic to, leaf 3 will send it out to leaves 1 & 2. yet leaf 2 will not send it out back to server 10.1.1.3 because it is not DF for this VNI, but what about User 2 which is single homed to leaf 2 in same VNI? how this BUM traffic will reach it? 2- in the case if server 10.1.1.3 picks leaf 2 to send the BUM traffic to, leaf 2 would send it over to leaves 1 & 3, in this case leaf 3 will forward back to server 10.1.1.3, as it is the DF for this VNI? Thanks and best of luck

This kind of visualization is greatly needed in the current Data Centers