So this part in our journey that we're going to configure this external BGP
speaker.
So I do have BGP capabilities on this Fortigate firewall, which is a .1, but I
thought just
to mix it up a little bit, let me bring in a Cisco device that we can run BGP
on.
So it's reachable at .121 on the 192.1 state, one network.
And for connectivity to this little router here, I have a console connection
from my
management computer.
So we can go ahead and do the configuration right there from a CLI.
So that's what we're going to do right now.
We're going to configure this BGP router to tell it that it's in the autonomous WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We're going to configure this BGP router to tell it that it's in the autonomous
system
6783.
We'll specify that it has a peer, a couple of peers actually at .61 and .62.
And those two peers, which are edge one and edge two respectively, those are in
autonomous
system 777.
All right.
So let's go to the command line interface on this Cisco device and let's
configure BGP.
And here we go.
So I named this our 6783 just to help remind us that this is the router going
to be supporting
the autonomous system 6783 as far as BGP goes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the autonomous system 6783 as far as BGP goes.
And I'm going to do a show IP protocols just to see what routing protocol.
Nothing.
So I have no dynamic routing protocols on this Cisco device whatsoever.
This happens to be a Cisco catalyst multi-layer switch, by the way.
Those type in configure space terminal, which takes us into configuration mode
on the Cisco
device.
And let's create a logical routing process for BGP, autonomous system 6783.
And to do that on the Cisco device, the command is router, BGP space, and then
the autonomous
system member that we want to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
system member that we want to use.
And so we want to use 6783.
We'll press enter and now we're in router configuration mode for BGP as part of
autonomous
system 6783.
So to specify our neighbors, the command is neighbor.
And so we'll type in neighbor.
And then the edge one is going to be at 192.168.1.61.
And if we just space in the question mark, we'll then see lots of options here.
We want to specify that that device is in the remote autonomous system.
So we'll type in remote dash as and that remote as that we're going to be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll type in remote dash as and that remote as that we're going to be
connecting
to where edge one lives is 777 and we'll press enter.
And I'm going to just pause right here for a moment because if that is
successful on
this Cisco device, they should get a little message saying, Hey, your BGP adjac
ency is
up, which is right there.
That's great news.
So let's go ahead and do it again.
But this time I want to appear with dot 62 and press enter.
And again, I'll wait for the console message to come up indicating that we have
a neighborhood
now with dot 62. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
now with dot 62.
And that may take just a minute.
And there it is.
All right, fantastic.
So now if we were to exit out of configuration mode here on the Cisco device
into a show
IP BGP summary and press enter, it's going to show us that we've got two BGP
neighbors.
And as far as over here on the far right, as far as how many prefixes we've
learned
from those neighbors, we have learned zero.
And that's because by default, the actual gateway zero isn't advertising any
routes via
BGP yet over to us.
And we could also look from the perspective of the gateway zero and see what WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we could also look from the perspective of the gateway zero and see what
the BGP status
is from its perspective.
So let's make a road trip over to our tier zero gateway at the CLI and we'll
take a look.
So I've just connected over via SH to our edge one edge transport node.
And from here, let's do a get gateways.
And here is our services router right there.
It is VRF number four.
So we just type in VR for press enter.
That's one of the easiest ways of working with and seeing the details regarding
that
services router.
So from here, if we did a get space in a question mark, if we scroll up here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So from here, if we did a get space in a question mark, if we scroll up here,
there's an option
for BGP.
So we'll type in get space BGP space question mark.
And then we have an option for neighbor, we'll type that in as well, a space
question mark
and let's use summary and press enter.
But a Bing, but a boom, we have a neighborhood ship with this device at dot 121
.
This is from edge one from the services router there.
And we are currently not learning any prefixes or networks from that neighbor.
And we're also not advertising any prefixes as of yet to that neighbor.
So regarding our game plan, as far as configuring the external BGP component WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So regarding our game plan, as far as configuring the external BGP component
here, that is done.
We now have BGP neighborhoods between this external device and the edge one, we
also
have one between ourselves and edge two.
So effectively, we've also just verified that external BGP neighborhood ship.
So fantastic.
So our next logical step then is to start advertising some routes via BGP
between these
peers.
And so we're going to start off based on our game plan by advertising some
routes from
the tier zero gateway up to this BGP speaker. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the tier zero gateway up to this BGP speaker.
And we'll do that in the next video.
I'll see you there in just a moment.