So for the R-TEP addresses, here's our game plan.
These edges currently are using the uplinks on their respective ESXi hosts for
the transport network.
So the edge one edge nodes at each site on different hosts are using the uplink
or a port group that leads to uplink VMNIC4.
And the edge two is at each site on their respective hosts are using a port
group for their uplinks that leads to VMNIC5.
So for all of these edge nodes, they can continue to use those same exact upl
inks on those respective hosts,
except we are going to use a different VLAN to carry the R-TEP traffic. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
except we are going to use a different VLAN to carry the R-TEP traffic.
And to make it very clear on which edge node is using which VLAN,
we're going to have edge one at site one here in blue, use VLAN71 with the IP
dressing space of 7171, etc.
And there's a default gateway at .1 and edge two at site one is going to use V
LAN72 and the IP dressing scheme of a bunch of 72s,
also with a default gateway of .1. And then over here at site two, a similar
process.
Edge one is going to use VLAN81 with 81s in the IP dressing with the .1 as a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Edge one is going to use VLAN81 with 81s in the IP dressing with the .1 as a
default gateway.
And edge two over here at site two is going to use VLAN82 with a bunch of 82s
as the layer three IP dressing,
once again using .1 as the default gateway.
Now behind the scenes, I have some top of rack switches that support all of
those VLANs.
And my top of racks, which is also have the .1 address on each of those VLANs
for each of those subnets to support the routing.
So my lab environment, I'm using some top of racks, which is to support that
functionality.
Or in a production environment, if site one is on the west-hand side of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Or in a production environment, if site one is on the west-hand side of the
country and site two is on the right-hand side of the country,
for the R-TEPs, they'd be using the IP dressing scheme and the default gateways
from our service providers or what leads to our service providers for that
connectivity.
So one thing we'll do here in the lab is we set up these R-TEP addresses.
I'll also be using my top of rack switch just to verify that once we set these
up, they are reachable from the external network.
And for the configuration of these R-TEP addresses, we could do it a couple of
ways.
We could locally go to each of these local managers and configure it there for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We could locally go to each of these local managers and configure it there for
their respective edge nodes.
Or there's also an option to do it here from the global manager.
And what I suggest is we demonstrate both options.
So let's start here with site one.
And we'll use the local manager to configure the R-TEP addresses.
And then we'll switch gears a little bit and we'll do site two edge node R-TEP
addresses using the global manager.
So to begin with, we'll start here at the local manager for site one.
And let's configure the R-TEP address for edge one on VLAN 71.
Also in preparation for that, let me go ahead to my top of rack switch and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also in preparation for that, let me go ahead to my top of rack switch and
begin a ping which should fail until we have that IP address in place.
So I currently have a remote session to the top of rack switch.
And let's do a ping to 71.71.71.71 which is the IP address that will be
eventually used by edge one for its R-TEP address.
And let's go ahead and do a repeat of let's say 100.
And let's also do a timeout of let's say 15 seconds.
And that way we can see that it's going to fail and fail and fail.
And then once we get it working, it should all work and finish off the 100. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then once we get it working, it should all work and finish off the 100.
So I just want to wait just for a moment until we get that first fail which
should be within 15 seconds.
And survey says there it is.
Okay, that period represents a failure of the ping and that's going to keep on
trying is going to fail until we actually get that IP address up and available
on our edge node.
So we minimize that.
And let's head over to our local manager here at site one, which is using the
virtual IP address of .10.
So logged in here to the local manager here at site one, we'll click on the
system tab.
So I'm going to verify I'm on the right device, so I'm going to click on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm going to verify I'm on the right device, so I'm going to click on
appliances.
And sure enough, we're at .11 and we have a virtual IP address of .10.
Fantastic.
We are on the right local manager.
So here at the site one NSX manager with the system tab selected on the left,
let's click on quick start under the configuration.
Now, if this tile right here, the configure remote to an endpoint, if that does
not show up once you've onboarded this NSX manager with the global manager, go
ahead and log out, log back in.
And this tile should appear. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And this tile should appear.
I had that happen more than once.
So now that it's here, we can go ahead and click here and get started.
And here, it gives me the option to go ahead and configure edge nodes for
stretch networking.
That means extending or stretching, for example, gateways and segments across
multiple sites.
So here's giving us the opportunity to go ahead and configure the remote tunnel
endpoints on our edge nodes.
So we want to do them all at once.
We can select them and we could put in the details here.
Or if you want to configure them one by one, which I do because I want to use
unique static IP addresses, we can then go ahead and click on one of those edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
unique static IP addresses, we can then go ahead and click on one of those edge
nodes.
And effectively, that took us under the fabric down to nodes with that node
selected.
And then from here, we go ahead and click on tunnels.
So here's the tunnel address for its tunnel endpoint.
And if we scroll down a little bit, we now have an option to set up the remote
tunnel endpoint.
And right here, I say, if you want to set up the remote tunnel endpoint, click
right here.
So we'll go ahead and click here to configure the remote tunnel endpoint for
edge one.
I'll go ahead and choose this default switch that our edge nodes are using.
I'll use the default teaming policy. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'll use the default teaming policy.
And then for the R-TEP VLAN, I want to use VLAN 71.
And then for the IP address assignment, I want to use a static IP address.
So I'll choose use static IP list.
And it's asking for the gateway first.
So the gateways can be 71.71.71.1.
We'll tab down the static IP address I want to use for the remote tunnel
endpoint is 77.77.77.77.
And the mask I want to use is a 24-bit mask.
So I'll put that in as well.
And then I got a message saying, hey, your gateway and your subnet don't match.
And that's because I put in 77s there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's because I put in 77s there.
I thought 71 in my mind, but I didn't type it in.
So there I have the 71.71.71 address with the default gateway at .1 on that
same subnet.
And we'll click on safe.
All right, that should be better.
Now, if that's successful, if we go back to our terminal session at the top of
rack switch
in just a moment here, once the edge node picks that IP address up,
and starts using it, that ping should begin to work.
So let's go ahead and just verify that it is now beginning to work.
And that's fantastic.
So I just want to verify that we had from the top of rack from the external WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I just want to verify that we had from the top of rack from the external
network
that that connectivity was working and that our edge one is actually using that
IP address,
which it is based on that ping succeeding now.
So all these were timeouts while we were doing the configuration.
And then we have the exclamation marks indicating successful things.
All right, let me minimize that.
And let's go on to edge two.
So we'll click on edge two and then we'll click on tunnels for edge two.
And once again, now we have the option of setting up the R tap for this time
edge two.
So we'll go ahead and click here, set the remote tunnel endpoint. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll go ahead and click here, set the remote tunnel endpoint.
We'll use the default switch that was deployed when we deployed this NSX edge.
I'll use the default teaming policy for edge two.
I want to use VLAN 72 and then I want to use a static address.
So let's use used static IP list, the default gateway is 72.72.1.
And the IP address we want to use is a bunch of 72.
So I'll put those in as well.
And then I'll tab down and we'll put the mask and then we'll click on save.
And then we'll rush over to our top of rack switch and let's do a ping to that
IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
IP address
at 72 72 72 and press enter and the configuration took hold on edge two faster
than I could get here because none of those timed out because it is up and
running.
So none of those two edge nodes have the remote type addresses.
Let's go over to the edge nodes over here at site two.
To do this one, instead of going to the local manager, we also could just do it
right here from the global manager that is working with site two.
So for site two, let's go to the global manager and we'll have it reach over
and configure these edge nodes with these R-type addresses using VLAN 81 and 82 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and configure these edge nodes with these R-type addresses using VLAN 81 and 82
with the IP addresses shown here edge one at site two, we'll use 81, etc.
Edge two, we use 82, etc.
Again, in those two respective VLANs.
And this time we'll use the global manager to do the configuration on these
edge nodes.
So here in the interface for the NSX global manager, let's confirm we're on the
right
device by going to system and sure enough, we are at the NSX global manager.
On the left, if we click on location manager, here it also confirms for us from
the right device and as we scroll down here are our locations. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the right device and as we scroll down here are our locations.
There's site one and site two.
So if we want to configure the R-type addresses for the edge nodes at site two,
we'll go to the site two section right here and here the site two section.
We'll click on the hyperlink here for networking.
So we'll click on networking.
And here it's showing us that for inter location communication, we have this
edge
cluster called lab two edge cluster available at site two.
And if we want to configure the R-tips on that edge cluster, we can click right
here
on configure and what it's doing is actually redirecting this over to site two.
So even though we're logged on initially to the global manager, it just whisked WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So even though we're logged on initially to the global manager, it just whisked
us
away through time and space over to site two.
So even though we started at the global
manager is simply a redirection at this point.
And if we want to get back, we can click right here on the NSX icon and that'll
give us back to the global manager.
So once again, right here, if you go to system and location manager, we're back
at the global manager.
So if we want to go back again, we can click here on networking for site two,
click on configure and again, it redirects us over to site two.
So if we want to go ahead and configure all the edges at once, if we're using a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we want to go ahead and configure all the edges at once, if we're using a
pool, for example, of IP addresses and can do all at one time, we can do that
or
we can click on each one and then do them individually.
So I've just clicked on the edge one over at lab two, which takes us to system
and under fabric nodes with lab two edge one selected.
And here we can click on tunnels and here is our current tunnel source IP
address of 777 and that's the tunnel endpoint that we can have on lab two edge
one. If we scroll down, we also have an option here to set up the remote tunnel
endpoint. So we'll do that by clicking here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
endpoint. So we'll do that by clicking here.
We'll use the default switch and for this one, we're going to use the VLAN of
81 and for addressing, we're using a static IP address and the default gateway
we
use is 81.81.81.1 and the static IP address that we want to use for this
remote tap address is going to be 81.81.81.81 and is a 24-bit mass.
So we'll put that in as well and then click on save.
All right. And that looks good.
So that's all in place.
Let's repeat that process except for edge two at site two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's repeat that process except for edge two at site two.
We'll use VLAN 82 and an IP dressing scheme of 82.
So we'll click here to configure the remote tunnel endpoint for edge two at
site two.
We'll use the default edge switch name that was deployed by default when the
edges
were deployed for the R-TEP VLAN.
Let's go ahead and use 82 based on our plan.
We'll specify a static IP address.
The default gateway is going to be 82.82.82.1 and the actual IP address is 82.
82.82.82. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
82.82.82.
And that is a 24-bit mask.
So with all that supplied, we'll go ahead and click on save.
So then we'll check our work.
So with edge two selected here at site two, we'll click on tunnels.
So here on the top, we have our tunnel endpoint.
And if we scroll down, it shows the details for our remote tunnel endpoint,
which includes the VLAN to use, the IP address to use, the mask to use and the
default gateway.
So as a test in my lab, I'm going to go back to my top of rack environment.
And let's test connectivity to these remote tunnel endpoints as well.
So if we did a ping to 81.81.81.81, that should work. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we did a ping to 81.81.81.81, that should work.
Fantastic. And let's also do a ping to 82.82.82 and that works as well.
So that gives me confidence that we have those IP addresses correct and that
those
R-TEP addresses can be used to communicate with the external network.
So at this point in our journey with our R-TEPs now configured for our edge
nodes
in both site one and in site two, our next logical step would be to go ahead
and create a gateway and a segment that both sites can use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and create a gateway and a segment that both sites can use.
And these referred to as stretch networking, stretch gateways and stretch
segments,
which are then going to be common.
So as far as our game plan goes, we'll create and test our stretch gateways and
segments in the very next video and I'll see you there in just a moment.
[BLANK_AUDIO]