All right, so the first step in our game plan
is to verify our existing topology that won't take too long.
Let's take a look at the routing table here on our Tier 0 gateway.
And one of the easiest ways of doing that
would be to go to an SSH session over to one of our edge nodes
and look at the routing table for that Tier 0 gateway from the edge node.
So let's start there.
Also, before we jump into the CLI, if we go to networking here in the NSX
manager
and then take a look at our network topology and we zoom in here,
we double click on our Tier 0 gateway, it'll show us the fabric view. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we double click on our Tier 0 gateway, it'll show us the fabric view.
And here we can just confirm and make it a little bit bigger.
Here we can confirm that for this Tier 0 gateway 0,
that we're using Edge 1, which is currently active and Edge 2,
which is currently standby.
So we're going to make an SSH session over to Edge 1
to verify our connectivity to that external segment
and also to verify the current routing table.
So here's Edge 1.
Let's do a get gateways and press Enter.
So here is our services router right here.
That's VRF number 4.
And then here is the distributed router for our Tier 0 gateway right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then here is the distributed router for our Tier 0 gateway right here,
this row right here.
Also, let me open up a second window to this Edge device.
I'd like to do a few commands from the VRF number 1, which is our distributed
router,
and also some commands from our services router, which is VRF 4.
So here in Edge 1, I've got two windows open.
And I'm going to go ahead and type a command down here of get gateways, press
Enter.
And then that's going to serve it up to both of my SSH sessions here
to the NSX CLI on the Edge.
So up here at the top, let me go ahead and go into VRF 1.
And that's our distributed router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's our distributed router.
So we'll go ahead and type in VRF space 1, press Enter.
And there's the prompt to reflect that right there.
And then on the second window here, let's go into VRF 4, which is our services
router.
So we'll type VRF not 5, but 4, VRF 4, and press Enter.
And there's our prompt there as well.
So now if we do commands like get forwarding, I'd like to show you something
that's pretty important to realize, and that is that the distributed router
and the services router from this output here,
they look like they are both sharing a lot of the same routing information.
But behind the scenes, there are some addresses that are only applicable, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But behind the scenes, there are some addresses that are only applicable,
for example, to the services router.
And that's our from our routing perspective.
We can forward packets that need to go to a services router to that device.
So if we scroll down in both of these and take a look,
so the command is the same, get forwarding on both.
But this is VRF 1 at the top and VRF 4 here on the bottom.
If I notice the routing perspective looks the same,
but there are some commands that are specific to the services router
that don't work on the actual distributed router.
For example, if we use command get route and press Enter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
For example, if we use command get route and press Enter,
that doesn't work on the distributed router,
but it does work like a champ here on the services router, which is the VRF 4.
So we're going to focus on that, let me expand that.
And currently here in VRF 4, we have our OSPF-learned route.
So the little O there from our previous skill represents an OSPF-learned route.
And there is the default administrative distance associated with OSPF.
Then we have a couple routes that are connected to our T1 gateways,
which have been advertised up to our Tier Zero gateway.
And that's why we know about them here at our Tier Zero gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's why we know about them here at our Tier Zero gateway.
And then we have an OSPF-learned route that we did as an example
of sharing routes from a physical router, running OSPF,
and advertising that route over here to our Tier Zero gateway.
The next two are the router to router subnets between Tier Zero and gateway A
and gateway B.
And then we have our backplane network.
Think of it like the logical subnet that we're going to use to communicate
between
our distributed router and services router here on gateway zero.
And then we have a directly connected network 192.1.81,
which is our connection to that physical external network segment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is our connection to that physical external network segment
and it's using Uplink 279 for that one.
So from here, if we wanted to verify we have reachability to that address,
we could go ahead and do a ping from this services router VRF.
So I'll ping to that address and that's looking good.
And let's also go ahead and ping the IP address of our default gateway,
which is our physical router on the physical networks.
We'll do a ping to 192.168.1.1.
And that looks good.
So I'll do a control C there.
And also in this VRF, for the services router,
if we did a get a space in the question mark, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if we did a get a space in the question mark,
we have several options, including route, which we looked at earlier.
We also have an option to look at BGP information.
So here if we type in get BGP space question mark,
and let's go ahead and ask for neighbor information,
space question mark and summary and press enter,
it's now showing us a summary of all the BGP neighbors it knows about.
So currently our tier zero gateway has no BGP neighbors configured yet.
And as a result, we have no neighbors.
But what we have done is verified our basic connectivity to this external
network.
And I'd actually like to do one more thing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I'd actually like to do one more thing.
And that is I'd like to verify that our tier zero gateway can ping
the IP address of .121, which will be,
once it's all configured, will be our external BGP neighbor.
So let's ping that as well as a test.
So do a ping to 192.168.1.121.
And survey says we're getting a response.
Fantastic. So we'll do a control C.
And that concludes our verification of the current infrastructure.
All right. So with our existing topology verified,
our next logical step then is to configure our tier zero gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
our next logical step then is to configure our tier zero gateway
and tell it that it belongs in a ton of system 777.
We're also going to go ahead and tell it that we have a peer
that we wanted to connect to at .121,
who's in the autonomous system of 673.
So we'll do all of that in the next video.
I'll see you there in just a moment.