In this Nugget, we're going to troubleshoot
a BGP topology that isn't working exactly like we should.
So for now, let's jump on a whiteboard,
take a look at the topology, and talk about what
the expected behavior is.
For our first troubleshooting BGP session, here's the goal.
Our goal, if I write it right here,
is to ping from the loopback address on R10 right there,
10.10.10.10, to the loopback address all the way over here
on R1 of 1.1.1.4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
on R1 of 1.1.1.4.
Yeah, throwing you for a loop there.
So we do have to have end-to-end connectivity all the way
from AS400 all the way to AS100, but it
needs to follow the most optimal path too.
You see, I created a link right here going from R4 to R3.
The link here on R2, if I just scratch out
these little interface labels real quick,
is FA4/0 on both of these resources, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is FA4/0 on both of these resources,
whereas the link here on R3 to R4 is using gigabit ethernet.
So it does need to go through the confederation
all the way over to AS200, but then the optimal path
dictates that it would go down the gigabit ethernet link
and then make its way over to R1.
Now, when we launch the virtual lab,
we're going to find out that this doesn't work.
And if I'm being totally honest, I
recorded this late in the evening a long time ago,
and I've forgotten what's broken.
So it's going to be a little bit of an adventure for me too. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So it's going to be a little bit of an adventure for me too.
So in the next Nugget, we're going to launch the virtual lab
and get going.
In the meantime, that's setting up scenario 1.
I hope this has been informative for you,
and I'd like to thank you for viewing.