So based on our plan, our next step is to go ahead and assign two new
interfaces to our Tier 0 gateway.
And one of those interfaces is going to use the actual services of Edge 1.
The other interface is going to be using the services of Edge 2.
And we'll use the IP addresses of .61 and .62.
And then for those interfaces, we'll also say that they connect to this
external segment 192,
which is our VLAN back segment, which in my network is the 192.61 network.
Also, what I'd love to do is show you prior to implementing those two new WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also, what I'd love to do is show you prior to implementing those two new
interfaces on the DR
and before we connect that effectively to the external router.
Currently, we have no services router yet, but the moment we take our Tier 0
gateway
and we connect it to an external segment like this one right here, at that
moment,
it will also add this logical services router to our Tier 0 gateway.
To confirm that, let's go ahead and take a look at before and then after we add
the connectivity
to the external network.
So for fun, I've got the Edge 1 on the top pane here and I've got ESXIA, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for fun, I've got the Edge 1 on the top pane here and I've got ESXIA,
our host transport node here at the bottom.
And let's just do a get gateways and press enter.
So here we have the same three distributed routers on the host transport node
and also on our edge.
And also we have VRF0, which is like the routing table for the actual VM itself
on the transport network.
Also, if we scroll to the right a little bit, it shows us for these three gate
ways
that they are distributed routers.
So distributed router for Tier 0 and there's the name over here on the left, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So distributed router for Tier 0 and there's the name over here on the left,
then for gateway A, distributed router at Tier 1, and then gateway B also a
distributed router at Tier 1.
But notice there's no services router anywhere on either of these nodes.
So our next step then is to go ahead and take this Tier 0 gateway and logically
connect it with two new interfaces
based on this plan and we're going to connect it to this external segment 192.
And when we do at that moment, that's going to automatically add this logical
services router component
to our Tier 0 gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
In fact, let's do one other really cool test because the host transport node is
not going to provide that connectivity
to the external network and not be directly connected.
It's not going to get a copy of the services router, but both edges will if we
include both edges
for the interfaces on the Tier 0 gateway.
So they closed the window here for the ESXIA host and let me add another window
that connects to edge two.
All right, so we have edge one of the top edge two at the bottom and just as a
starting point,
let's do a get gateways and press enter and notice that both edge one and edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's do a get gateways and press enter and notice that both edge one and edge
two have all three distributed routers
and neither of them yet have any services router function.
So let's change that by adding some interfaces on this Tier 0 gateway that are
connecting to that external segment.
So to do that, we're going to go to networking, which we're currently on, and
then we're going to go down to our Tier 0 gateway
and it's here the Tier 0 gateway where we're going to edit it and specify that
for interfaces.
We want to have an interface using edge one that's connecting us to that VLAN
back segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
back segment.
So we'll click on the three dots here and then for the menu, we'll click on
edit.
So we're editing the details for our Tier 0 gateway called our Tier 0 gateway
zero.
If we scroll down under interfaces, we'll expand that and then from here, we'll
simply click on set.
And currently we have no external interfaces.
So we'll simply click here to add.
So this is like taking a router and physically adding a interface is going to
connect to a network.
And so for this first interface, let's call this dot 61 because that's the IP
address we want to use via edge one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
address we want to use via edge one.
And that way, when we see the name of this interface that we're adding, we'll
know, oh, that interface called dot 61 via edge one is being provided by our
edge one transport node.
And then for the type, it's going to be external and then for the IP address,
we want to use 192 dot 168 dot 1 dot 61 with a 24 bit mask.
So we'll plug that in.
And then if we tab over now, it's asking us, where do you want to connect this?
And we're going to use the drop down say, you know what, we want to connect
this to our VLAN based segment called external segment 192. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this to our VLAN based segment called external segment 192.
And that's how these are all glued together.
Now, there is an additional thing we need to specify and that's this if we're
going to use edge one to support this logical interface on our tier zero
gateway.
We'd also want to make sure from our drop down for edge node, we choose the
right edge device.
So these are our two edge nodes that are in our edge cluster.
So we'll choose edge one and we are good to go.
So we specifically the logical name of this interface.
We specified the type or connecting to an external network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We specified the type or connecting to an external network.
We specify the segment we're connecting to.
We specify the logical IP address we want to use and the edge node that we want
to actually do the work for us for that connectivity to the physical network.
So with that in place, we'll go ahead and scroll down and click on save.
All right, so we have one interface via edge one.
Let's go ahead and create the second one.
In fact, right here, it says uninitialized.
We can click on a little refresh there and there it is.
Good to go.
Let's create one more for dot 62 as a second interface connected at same
segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
segment.
But this time we'll use edge to four fault tolerance purposes.
So we'll click on add interface.
We'll call it dot 62 via edge dash to the type is going to be external for the
external connection.
And then we'll choose the segment ext seg 192, which is our VLAN base segment.
So the IP address we want to use for the second interface is 192.168.1.62 with
a 24 bit mask will plug it in and then from the edge node will click on the
drop down and now showing us the remaining edge node.
We only have two of them, so we'll pick edge to this going to support this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We only have two of them, so we'll pick edge to this going to support this
logical interface on our gateway.
So we'll scroll down, click on save and that looks good.
So we'll click on close, then we'll scroll down and click on close editing and
we can collapse all this.
So now we have our tier zero gateway and it has two linked tier one gateways.
That's gateway and gateway B.
If we expand it, it's now showing us here under interfaces that we have two
interfaces.
And if we click here, it'll confirm what those are.
So we've got the two interfaces with the IP addresses, 192, once it's 81 and 62 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we've got the two interfaces with the IP addresses, 192, once it's 81 and 62
respectively.
There is their names and each of them are being supported if we expand those by
a respective edge node.
So this one is being supported by edge one.
And if you look at the other one and scroll down, it's being supported by edge
two and they're both connected to our external VLAN back segment called ext seg
192.
So we'll close that and then just for confirmation, let's click on network top
ology.
Let's zoom in on our T zero gateway and notice that it has two interfaces here,
the 192, Wednesday, 161 and 192, Wednesday, 162. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the 192, Wednesday, 161 and 192, Wednesday, 162.
And if we double click on this tier zero gateway, it's going to show us the
details behind the scenes of what's supporting that.
So currently edge one is active and edge two is the standby.
So that looks great.
Let me go back to our tier zero gateway.
Let me remove one of those interfaces because I want to show you and compare in
contrast edge one versus edge two.
So we'll go back to this gateway.
We'll click on the three dots.
We'll click on edit and we'll say, you know what, for interfaces, we're just WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll click on edit and we'll say, you know what, for interfaces, we're just
going to give you one for the moment.
So I'll go back into interfaces and then I'm going to take the one via edge two
and simply delete it and then click on delete and then click on refresh.
And that just has one interface.
So we click on close and close and we collapse that's just for tightiness.
We go back to network topology and take a look at the top here and scroll up.
Now our tier zero gateway only has one connection and if we double click on it
is showing that it's going to be supported here just by edge one.
Now the reason for that too is I want to show you the differences on edge one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now the reason for that too is I want to show you the differences on edge one
versus edge two.
So if we look at edge one because we're now connected to an external segment
here, edge one is going to have a services router component running on it and
edge two because it's not directly connected or used to connect to the physical
.
Network and not providing that service edge to is not going to have the
services router as a result.
So here are edge one and edge two from our output before.
So we'll do a get gateways again press enter.
So check this out edge one now has this SR services router component with its
own UUID has its own VRF and there's the name and you'll notice edge to does WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
own UUID has its own VRF and there's the name and you'll notice edge to does
not have a copy of that services router function because at the moment edge to
is not being used as part of that connectivity from the tier zero gateway to
the physical network.
So if we went back and we changed that we go back to our tier zero gateway we
go back and we edit our tier zero gateway once again and then we go down to
interfaces and we click here on the link for interfaces and then we add the
interface back in.
We'll call it dot 62 via edge to make sure that we're selecting edge to be used WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll call it dot 62 via edge to make sure that we're selecting edge to be used
as part of this looks like the external segment and then we'll put in the IP
address here and then we'll scroll down and click on save and we'll confirm our
work here.
We'll refresh that make sure it says success that looks great will click on
close.
So now if we go to network topology for our tier zero gateway it once again has
two interfaces and if we double click on the tier zero gateway to look at the
fabric is now showing us the edge one and edge to are both participating.
So this is active it says edge to unknown.
So in a moment or two that'll turn to standby and show as standby. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in a moment or two that'll turn to standby and show as standby.
However now that edge to is involved as a logical interface and providing
connectivity or could provide connectivity to the external network on this tier
zero gateway edge to will also now have a copy of that services router.
So we click on refresh that looks better.
So there's edge one active edge to standby and let's take a look at the CLI as
well.
So back at the CLI for both those two a moment ago just edge one had the
services router component for the tier zero gateway and edge to do not.
So if we have the upper key and do get gateways again now they both have a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we have the upper key and do get gateways again now they both have a
services router function associated with our tier zero gateway zero.
[no audio]