Now that we've got one of the troubleshooting
tasks under our belt-- we've used some of those show
commands-- it's time to take it up a notch
and look at some other issues that
may arise in a BGP environment.
Let's jump on the whiteboard one more time,
take a look at the topology and talk
about that expected behavior.
Now it's time to set up Scenario 2 in our BGP Troubleshooting
Lab.
We see we've got the same topology here,
and the goal for this Nugget is going
to be very similar, except I'm going to reverse the direction.
I want to ping from R1's loopback of 1.1.1.4, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I want to ping from R1's loopback of 1.1.1.4,
to R10's loopback of 10.10.10.10.
And here's the kicker.
We're going to want to use the exact same optimal
path, this time going up through R3 over to R4
through the confederation, and then make its way down to R10,
but a different set of problems has arisen in this Nugget.
So the things that we troubleshot in the last Nugget
and fixed, we're not going to have them this time.
It's not going to be that easy.
So let's fire up the virtual lab, and get going.
In the meantime, that's been setting up Scenario 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
In the meantime, that's been setting up Scenario 2.
I hope this has been informative for you,
and I'd like to thank you for viewing.