Thank you Terry! I've been struggling to understand how to make new circuit connections on our NEXUS 7ks. While the CLI isn't identical this video explained the whole process perfectly. You da man!
Terry Vinson Thank you for your honest awnser. I was asking because I'm suscribed to IPexpert, but their videos are now a mix of different trainers.....So I had a suspicion. Good luck!
Incredibly simple explanation of a very complex topic. I am currently in a CCNA class at UMUC. This was extremely helpful in explaining the Layer 2 adjacency issue I have been researching. So this could apply to adjacency in subnets as well as multiple VLANS, correct?
Excellent explanation! With L3 MPLS VPN, the customers routes are kept separate in the provider's cloud after they're redistributed into MP-BGP routes (by the addition of a Route Distinguishers to the prefixes. How are customers prefixes kept unique when utilizing EoMPLS? Does the xconnect command create some sort of tunnel across the provider's cloud?
That is exactly what is happening. The two CE devices are connected via a tunnel across the service provider cloud. What we are looking at is "layer 2" adjacency cross that cloud. Layer 2 in this instance is ethernet.
So R4 and R5 do not have igp configured on them? If IGP was configured on them then they could have reached each other right? So what is the scenario here that prevents R4 and R5 from running IGP?
No, you still have to add the wildcard and an area statement. What u need is "network 0.0.0.0 255.255.255.255 area 0" which will advertise every interface on the router as area 0.
Bruce I don't really understand the question. Typically something like EoMPLS is used to provide L2 Adjacency, where a GRE or mGRE can do similar things typically in the Absence of MPLS. This is used to leverage the underlying MPLS transport. But if you just ran MPLS between sites and you can hit tunnel destination IP from the IP you wish to use as the source you can do GRE, IPnIP or DMVPN between sites if you wanted or needed too. This only really difference is that MPLS gives you TE capability in the cloud with QoS awareness. HTH
@@TerryVinsonCCIEx2 Terry, I have a hub and spoke type architecture that is currently running across 15 T-1s. There is a push to replace them and convert to IP. This wouldn't be difficult using DMVPN, but this system needs VLANS. So how can I extend the VLANS to these 15 sites?
iam sorry mr. but iam forget to no shut interface direct connected to R3. it is therefore not up interface tunnel R2#show mpls l2transport vc 20 and R3#show mpls l2transport vc 200. big thank master
@@peternorton7665 yeah. That was from an enterprise class on MPLS and I wanted to illustrate how cool the protocol was. If it was SP I would have done BGP and a L3VPN.
@@TerryVinsonCCIEx2 gave it more though , just talking shop, even if it was nor a SP and you needed a couple of VRF , DO L3VPN....i found myself doing it in a smaller network that needed separation
@@peternorton7665 I agree. Not much use for the technology if you can't isolate. But in that class the focus was on MPLS as a protocol. The crappy part is that there was no indication of why it's important to learn MPLS in that class. Cool stuff like L2VPN, L3VPN and TE. So I was just trying to add to the official class and made videos as supplemental viewing for those students.
Amazing explanation, 10 years after you recorded this, thanks!
Your videos are still useful after about 7 years! Well Done and Thank you !
Well thats good to hear. I plan on spending half my time on UA-cam in 2021. So keep an eye out for more content.
Thank you Terry! I've been struggling to understand how to make new circuit connections on our NEXUS 7ks. While the CLI isn't identical this video explained the whole process perfectly. You da man!
Excellent explanation! Right to the point, easy to understand!!! Thaks for sharing!
Great explanation,easy to understand ,good to know what is happening on the road between our remote DC routers
As simple and as informative it can be..!! Thanks @Terry
Awesome as usual. Definitely a top notch instructor!
I'm here because of you, but six years later:)
Thank You Very Much for the Video. Well explained
Excellent teaching method.
Easily explained.. Greet !!!! Thanks....
thanks for share your knowledge :-)
great explanation
You are a master at this!!!!!!! The explanation goes to the point, no blablablabla as others do. Thanks
And I am subscribing just after watching this :D
Pepin Nator Thanks Pepin.I am so busy I haven't had time to record more free videos. Maybe after the RSv5 is finished.
Very nice thing to say! :)
Terry Vinson Are you still with IPexpert?
***** No I am not. Currently, I just teaching as an independent contractor.
Terry Vinson Thank you for your honest awnser. I was asking because I'm suscribed to IPexpert, but their videos are now a mix of different trainers.....So I had a suspicion. Good luck!
Salute
easy and clear
thanks.
Incredibly simple explanation of a very complex topic. I am currently in a CCNA class at UMUC. This was extremely helpful in explaining the Layer 2 adjacency issue I have been researching. So this could apply to adjacency in subnets as well as multiple VLANS, correct?
Excellent explanation! With L3 MPLS VPN, the customers routes are kept separate in the provider's cloud after they're redistributed into MP-BGP routes (by the addition of a Route Distinguishers to the prefixes. How are customers prefixes kept unique when utilizing EoMPLS? Does the xconnect command create some sort of tunnel across the provider's cloud?
That is exactly what is happening. The two CE devices are connected via a tunnel across the service provider cloud. What we are looking at is "layer 2" adjacency cross that cloud. Layer 2 in this instance is ethernet.
So R4 and R5 do not have igp configured on them? If IGP was configured on them then they could have reached each other right? So what is the scenario here that prevents R4 and R5 from running IGP?
Hi Terry! Is EoMPLS or AToM the same thing as VPLS and Pseudowire?
Does that "network 0.0.0.0" command work for OSPF too?
No, you still have to add the wildcard and an area statement. What u need is "network 0.0.0.0 255.255.255.255 area 0" which will advertise every interface on the router as area 0.
Can this configuration be encrypted and sent over a gre multipoint tunnel?
Bruce I don't really understand the question. Typically something like EoMPLS is used to provide L2 Adjacency, where a GRE or mGRE can do similar things typically in the Absence of MPLS. This is used to leverage the underlying MPLS transport. But if you just ran MPLS between sites and you can hit tunnel destination IP from the IP you wish to use as the source you can do GRE, IPnIP or DMVPN between sites if you wanted or needed too. This only really difference is that MPLS gives you TE capability in the cloud with QoS awareness. HTH
@@TerryVinsonCCIEx2 Terry, I have a hub and spoke type architecture that is currently running across 15 T-1s. There is a push to replace them and convert to IP. This wouldn't be difficult using DMVPN, but this system needs VLANS. So how can I extend the VLANS to these 15 sites?
@@bsedlak510 That's rough. In these situations I use VXLAN if the equipment will support it. If not, it's hard to say what the best options would be.
sorry mr, i want to ask question.
R2#show mpls ldp neighbor
Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 2.2.2.2:0
TCP connection: 1.1.1.1.646 - 2.2.2.2.30328
State: Oper; Msgs sent/rcvd: 20/20; Downstream
Up time: 00:10:34
LDP discovery sources:
FastEthernet0/0, Src IP addr: 10.1.12.1
Addresses bound to peer LDP Ident:
10.1.12.1 10.1.13.1 1.1.1.1
Peer LDP Ident: 3.3.3.3:0; Local LDP Ident 2.2.2.2:0
TCP connection: 3.3.3.3.64196 - 2.2.2.2.646
State: Oper; Msgs sent/rcvd: 15/15; Downstream
Up time: 00:06:30
LDP discovery sources:
Targeted Hello 2.2.2.2 -> 3.3.3.3, active, passive
Addresses bound to peer LDP Ident:
10.1.13.3 3.3.3.3
R2#
R3(config)#do sho mpls ldp ne
Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 3.3.3.3:0
TCP connection: 1.1.1.1.646 - 3.3.3.3.44304
State: Oper; Msgs sent/rcvd: 29/28; Downstream
Up time: 00:18:18
LDP discovery sources:
FastEthernet0/1, Src IP addr: 10.1.13.1
Addresses bound to peer LDP Ident:
10.1.12.1 10.1.13.1 1.1.1.1
Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 3.3.3.3:0
TCP connection: 2.2.2.2.646 - 3.3.3.3.64196
State: Oper; Msgs sent/rcvd: 24/23; Downstream
Up time: 00:13:49
LDP discovery sources:
Targeted Hello 3.3.3.3 -> 2.2.2.2, active, passive
Addresses bound to peer LDP Ident:
10.1.12.2 2.2.2.2
R3(config)#
R3#show mpls l2transport vc 200
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
Fa0/0 Ethernet 2.2.2.2 200 ADMIN DOWN
R3#
R2#show mpls l2transport vc 200
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
Fa0/1 Ethernet 3.3.3.3 200 ADMIN DOWN
R2#
why when i show mpls l2transport vc 200 is donw ?
maybe you can help me what is a root cause a problem ?
thanks
iam sorry mr. but iam forget to no shut interface direct connected to R3. it is therefore not up interface tunnel R2#show mpls l2transport vc 20 and R3#show mpls l2transport vc 200. big thank master
He did not configured bgp
Don't need BGP for this demonstration. It's a pure MPLS exercise.
@@TerryVinsonCCIEx2 true...i actually realized that afterwards, you just build the PE core......
@@peternorton7665 yeah. That was from an enterprise class on MPLS and I wanted to illustrate how cool the protocol was. If it was SP I would have done BGP and a L3VPN.
@@TerryVinsonCCIEx2 gave it more though , just talking shop, even if it was nor a SP and you needed a couple of VRF , DO L3VPN....i found myself doing it in a smaller network that needed separation
@@peternorton7665 I agree. Not much use for the technology if you can't isolate. But in that class the focus was on MPLS as a protocol. The crappy part is that there was no indication of why it's important to learn MPLS in that class. Cool stuff like L2VPN, L3VPN and TE. So I was just trying to add to the official class and made videos as supplemental viewing for those students.