And welcome back.
As we continue our journey, we're going to configure this Tier 0 gateway.
And behind the scenes, it's really the services router function on this Tier 0
gateway
that we wanted to go ahead and be a BGP peer with this device out here at .121.
And the Tier 0 gateway is going to be in a Thomas System 777.
And the soon-to-be configured external BGP router is going to be in the Thomas
System 6783
based on our plan.
So to configure the details for our BGP configuration on our Tier 0 gateway, we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So to configure the details for our BGP configuration on our Tier 0 gateway, we
're going to go
to the NSX manager right here.
And we'll click on networking.
And then because this is going to be associated with our Tier 0 gateway, we're
going to go
ahead and click under Connectivity.
We're going to click on Tier 0 gateways.
And we have one of them.
And that is right here.
So if we expand it currently, if we scroll down, BGP is enabled by default, but
it has
all the default configuration.
So if we want to modify the BGP configuration, we'll go ahead and click on the
three dots
for our Tier 0 gateway.
And we'll click on Edit from the dropdown menu. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we'll click on Edit from the dropdown menu.
So now we can scroll down to the BGP section, expand it, and put the values
that we want
here.
So it is enabled.
We'll go ahead and leave it enabled.
And our local AS, our local autonomous system, is going to be 777.
And for most of the other details here, I'm going to go ahead and leave them at
their
default, except we do need to specify who the neighbor or neighbors are going
to be for
this Tier 0 gateway.
So still here in the BGP section, over here where it says BGP neighbors, we'll
go ahead
and click on Set.
So we'll click on Set here.
Currently there's no BGP neighbors configured. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Currently there's no BGP neighbors configured.
So we'll fix that by clicking right here on Add BGP neighbor.
So the IP address of our BGP neighbor is going to be 192.168.1.121.
We verified that we could ping that from our services router.
So we know we have basic connectivity there.
And then the remote autonomous system number for that soon to be BGP neighbor
is going to
be 6783, just like that.
And then for the source address, we could specify an IP address we want to
source the
BGP neighbor ship from on the Tier 0 gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
BGP neighbor ship from on the Tier 0 gateway.
But if we just leave it blank here, it'll simply use the routing table and use
whatever
interface it would use from a routing perspective to connect and build a
neighbor ship with
that pair.
So with BGP, it's not using its own proprietary protocol layer 4.
It uses TCP and some well-known ports associated with TCP.
They're associated with border gateway protocol.
So because they're on the same exact subnet, I don't need to change the maximum
hop limit.
So we'll scroll down and I'm going to leave all the other defaults as they are.
So the other thing I did here for the neighbor was specify the IP address of
the neighbor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the neighbor
and also specify the autonomous system number of the neighbor.
So I'll scroll down, click right here on Save.
So another that's configured over here on the right under Status.
I'm going to click on the refresh and Survey says Success.
Fantastic.
Click on Close.
Then I'll click right here on Save.
And I'll scroll down and click right here on Close Editing.
And boom.
Now we have our BGP neighbor from the perspective of the Tier 0 gateway.
We now have that neighbor configured.
And I see over here on the right, I see an alarm.
So if we click on that and look at the details, visit showing us that we have B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we click on that and look at the details, visit showing us that we have B
GP down.
Now why would it be showing down twice?
Well, it's showing once as BGP being down from Edge 2 and the other one, if we
look at
it, I'll betch it's Edge 1.
And there it is.
So effectively, both of our Edge nodes are saying, you know what?
We're trying to form this BGP neighborhood out there to that device at 121, who
's in
autonomous system 673, but we're having absolutely no success with it at all.
And there's a good reason for that, which is we haven't yet configured the
external device. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
external device.
So that, my friend, will be our next logical step is to go to this device,
which in my
lab topology, that's a Cisco device.
It's going to be running BGP and let's set it up.
So when we set it up, we're going to tell it that it should peer with .61,
which is Edge
1 and .62, which is Edge 2.
And as part of our configuration, we'll specify that this BGP speaker is in
autonomous system
673 and that the remote autonomous system for .61 and .62 are both in
autonomous system
777.
So I'll see you in the next video as we can figure that external device as an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'll see you in the next video as we can figure that external device as an
external
router running BGP.