So based on our plan, we have our tier zero router.
It's got two interfaces behind the scenes
because they're connected to an external segment.
These services router function has been implemented on our edge nodes.
And now it's time on our tier zero router to serve a virtual IP address.
So we're going to use 192.168.1.60.
So let's go to the NSX manager and do that right now.
So here at the NSX manager,
we'll click on the networking tab on top and on the left,
we'll click on tier zero gateways and then we'll simply go into the details
for our tier zero gateway and edit it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for our tier zero gateway and edit it.
So we'll click on the three dots and then from the menu, click on edit.
And then from here where it says the HA VIP for the virtual IP, we'll click on
set.
And then we'll click on add HA VIP configuration.
And then we'll specify the IP address we want to use.
So if we want to use 192.168.1.60 with a 24-bit mask, we specify that.
And then we need to also specify the interfaces
that are going to be logically behind the scenes supporting that.
And so it says select exactly two interfaces for our fault tolerance. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so it says select exactly two interfaces for our fault tolerance.
So we'll choose the first logical interface being provided by edge one.
Then we'll also choose the second interface of .62 via edge two and we are good
to go.
So we'll click on add and then click on apply and then click on save.
And we'll scroll down and we'll click on close editing.
So from my management computer, I'm also on the 192.168.1 network.
If that all works, I should be able to ping that virtual IP address
that we just configured right here from my management computer.
So let me bring over a command prompt and let's test that with a ping WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let me bring over a command prompt and let's test that with a ping
to 192.168.1.60 and survey says no problem.
And we could also confirm that if we took that away, let's click on close
and let's click on edit.
So we'll edit the properties of our gateway.
We'll go back to the HA VIP and let's go ahead and we'll delete that
and click on delete and apply and save.
So now that we don't have a virtual IP address set at .60,
if we bring back that command window again, hit the up arrow key and press
enter,
we get no response just to confirm that that wasn't some other IP address on my WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we get no response just to confirm that that wasn't some other IP address on my
192.168 network that I wasn't aware of.
So it's not working right now, but if we go back and put it in by clicking on
set and add
and then we put it back in and then we select our interfaces to support that
and then click on add and click on apply and save and scroll down and click on
close editing.
Now we go back to our command prompt and hit the up arrow key.
That should respond once again.
All right, let me close that and let's go back to our network topology.
So there's our tier zero and then we have an inter router link from our tier WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So there's our tier zero and then we have an inter router link from our tier
zero down to gateway
A and then gateway A is connected to the 10 segment and then off that yellow
segment we have two VMs
and they are VM1 and VM3.
VM1 being hosted by ESXIA and VM3 being hosted by ESXIB.