So one aspect that's really critical to success oftentimes is to plan out stuff
before you do it.
In that way, we're not just haphazardly putting in commands, we actually have a
strategy.
So as far as our game plan for BGP, let's go ahead and set up our Tier Zero
Gateway,
which is currently connected to this 192.168.1 network. Also, as a reminder,
anytime we're connecting our NSX-Routed environment to an external network that
connectivity between the NSX and the physical world, that's going to use these
services
of one or more of our edge nodes. So if we're doing active standby or active WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of one or more of our edge nodes. So if we're doing active standby or active
active,
either way, we're going to be using the services of our edge node or nodes for
that functionality.
So we've already put the connectivity to the physical network in place a couple
of skills ago,
and now regarding BGP, let's do the following. This little router right here
that we used with
OSPF, it's at .1. And actually, we had the scenes that say 4 to 8 firewall that
's doing layer three
services, but we have a .1 address on that 192.168.1 network. So as far as our
game plan goes,
we'd be wise to take a moment and just verify our existing topology that we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we'd be wise to take a moment and just verify our existing topology that we
really do still
have access to this external network segment. So our first order of business is
going to be
verifying the existing topology. And then once we've verified that, let's go
ahead and start the
configuration for our Tier Zero Gateway and set it up for BGP and for the
autonomous system number.
Let's use autonomous system because it's just to my lab environment. Let's use
autonomous system
number 777. Does it feel lucky? I hope so because it's getting 777. Now, as
part of that
configuration behind the scenes, it's really going to be leveraging our Edge 1 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
configuration behind the scenes, it's really going to be leveraging our Edge 1
and Edge 2
transport nodes for any BGP connectivity that we're going to have with the
outside world.
So just as I note, we're going to use Edge 1 at .61 and Edge 2 at .62 for the
actual pairing.
And for the external BGP neighborhood to the external network, because we've
already used
this device once, let's go ahead and let me add a new device to our topology.
So I'm going to go
ahead and put a device right here. And this is going to be a Cisco device that
's running BGP.
So for BGP on this device, let's go ahead and use BGP with the autonomous WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for BGP on this device, let's go ahead and use BGP with the autonomous
system number 6783.
So as far as our game plan, we'll go ahead and peer with that Cisco device. And
its IP address
is .121 on this external network. So we'll say peer with .121 on that 192.1.81
network.
And also that that peer is going to be an autonomous system 6783. So our Tier 0
gateway will be an
AS777. The device we're peering with with BGP is going to be an autonomous WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
AS777. The device we're peering with with BGP is going to be an autonomous
system 6783,
which means that once we have that BGP neighborhood in place, it'll be an
external BGP
neighborhood. And any routes we learn should have the associated administrative
distance
that's associated with an external BGP learned route. Now in BGP, it takes two
to tango. So
once we configure the Tier 0 gateway and tell it that it's in AS777 and that it
's got an external
neighbor that we want to peer up with, we also need to configure the external B
GP neighbor. So
let's say on external BGP config. And I'll put a little arrow here saying we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's say on external BGP config. And I'll put a little arrow here saying we're
going to peer
back with this Tier 0 gateway, which is at autonomous system 777. So then once
we've set up that
BGP relationship between Tier 0 and this BGP speaker up here, we should
probably pause for a
moment and just verify that the E BGP neighbor ship exists and that is
functional. And we can
verify the external BGP neighbor ship, both here at the Tier 0 gateway by
connecting to one of our
edge nodes and looking at the information there for the services router
function. And we can also
take a look at the BGP neighbor ship from the perspective of the external WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
take a look at the BGP neighbor ship from the perspective of the external
router. In this case,
it's going to be a Cisco device running BGP in autonomous system 6783. So once
we verified our
external BGP neighbor ship between these two devices, I propose then that we
start to add routes that
we're going to advertise inside of BGP to each other. So let's start off with
advertising routes
from Gateway 0, that's our Tier 0 gateway. And we'll verify those shared routes
show up here
inside this Cisco BGP router. And then secondly, let's also do it the other
direction. We'll
advertise some routes from our external router and make sure those routes show WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
advertise some routes from our external router and make sure those routes show
up here in the
routing table on our services router at our Tier 0 gateway. So as we dig into
this game plan,
looks pretty logical step by step. So in our next video, let's take a moment
and just verify our
existing topology as we begin to execute our game plan.