So in our journey, we just finished configuring the external interfaces on our
T0 gateway.
And next, we're going to go ahead and do the IP routing and the source net.
So let's start with the IP routing and we'll set up a default route on the T0
gateway,
a default route that goes through the service provider connecting site one to
the internet,
and another default route for the service provider at site two.
And those addresses of the external gateways are 23.1.2.1 for site one.
And at site two, the default gateway address for the service provider is 24.1.2 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And at site two, the default gateway address for the service provider is 24.1.2
.1.
And the cool thing is with NSX Federation when setting up these default routes
or any routes to that matter,
is that we can associate those routes with a specific site.
So we'll create the default static route here on site one with this next top
and the default route here at site two with this next top.
So let's head back to the global manager and let's implement those two default
static routes.
So to go back to the global manager, when we left off, we were at site one.
So from the drop down here, we'll go back to the global manager.
So currently says we're back at the global manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So currently says we're back at the global manager.
Fantastic. That's also indicated right here.
And let's click on networking right here in the interface for the global
manager.
So with networking in the top selected on the left on our connectivity,
we'll click on our tier zero gateways.
So there's our current tier zero gateway called stretch T0.
And if we want to set up a default route for our tier zero gateway,
we'll simply click on the three dots, click on edit from the menu,
and then scroll down to the routing section.
So down on the routing, we'll expand that.
And then down here under static routes, we'll click on set. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then down here under static routes, we'll click on set.
So by default, no static routes.
So we'll click on add static route.
And let's call this one default or site one via ISP dash a and this little note
there.
That's going to be through our local VLAN 23.
So that's just the label.
So when we see it will know what it is.
And then for the default route for IPV four, that's going to look like four z
eros and a slash zero.
And then we need to specify the next top.
So service brother A, the next top is going to be 23.1.2.1.
So to do that here in the column for next hops, we'll click on set right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So to do that here in the column for next hops, we'll click on set right there.
And then we'll click on set next tops.
And we'll go ahead and say the next top is going to be 23.1.2.1.
And for the administrative distance, I'm going to put it 150.
Now the administrative distance is only important if there's multiple default
routes
coming in from different sources.
So later, if we have a default route that's being learned, for example, from
external BGP
or some other method and it has a lower AD, the route with the lower AD is
going to win
and be placed in the routing table. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and be placed in the routing table.
So I'm going to use 150 here at the moment.
It's going to be the only default route for site one.
And then for the scope, this is also super important.
I'm going to click here for scope and say this is going to apply just to site
one.
Alternatively, we could also specify specific interfaces.
But I'm going to go ahead and say all of site one and click on add.
And then we'll click on apply and then click on save.
So now our tier zero gateway has a single default route via service provider A
over at site one.
So let's do a similar treatment.
But for a default route through service provider B, which is over at site two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But for a default route through service provider B, which is over at site two.
So we'll click on add static route.
I'm going to put the name in.
So I just copy pasted their default for site.
We want this to be two through ISP B as in boy.
And that's going to be using our local VLAN 24 for access to that service
provider.
And then the actual route itself is going to be the 0, 0, 0, 0,
slash zero.
That's the syntax for a default route for IPv4.
And then we'll click here on next tops.
We'll click on set and click on set next tops.
And for ISP B, it's at 24 dot 1 dot 2 dot 1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for ISP B, it's at 24 dot 1 dot 2 dot 1.
And then I'm also going to do the same administrative distance.
And the scope is going to be for site two.
So I'll specify site two there.
Click on add and then click on apply.
And then click on save.
And now we have two default routes.
And just to confirm the next tops for ISP, the next top is 23 dot 1 dot 2 dot 1
.
And for the default route for site two, if we click here on the hyperlink for
next tops,
it's 24 dot 1 dot 2 dot 1.
And the scope is site two fantastic.
So we'll go ahead and close that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll go ahead and close that.
That all looks good.
And we'll click on close and it'll scroll down and click on close editing.
And we should also be able to verify that at either of our edges as well.
So let me go ahead and SSH back over to edge one at site one.
And from here, let's do a gate gateways.
So it's VRF 13 for our stretch tier zero services router.
So what we'll do is type in VRF 13 to go into that VRF and let's do a get route
and press enter.
And we should have a default route with the next top of 23 dot 1 dot 2 dot 1,
which we do.
We could also see the same information with a get forwarding just like that, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We could also see the same information with a get forwarding just like that,
which also confirms that we have our default route.
And we already verified in a previous video that we can ping that address.
However, since we're here, let's just verify once again that we can ping 23 dot
1 dot 2 dot 1.
And that looks good.
And if the service provider has everything else set up for us to reach the
internet,
we should be able to from this VRF for our services router for the tier zero
gateway.
We should be able to go out to the internet.
Let's try a ping out to 8888.
And that is work.
It's we'll do a control C. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's we'll do a control C.
And let's also do a trace route out to 8888.
Just to verify we really are going out to the internet.
And that trace route didn't look too happy.
So let's go ahead and source that from our 23 dot 1 dot 2 dot and edge 1 is at
dot 61.
Let's see if that gives us any better success.
Ah, there we go.
I'll cancel that.
So apparently initially when I traded it without specifying the actual source
address,
it was using an address that wasn't reached.
We'll back through that same service provider.
However, when I told to explicitly use the edge node address 231261, it worked WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
However, when I told to explicitly use the edge node address 231261, it worked
no problem.
So another we have our IP routing set up with a default route.
We tested it through service provider one.
We could also verify that from an edge node over here at site two is very
likely
of the same success in going out to 24 dot 1 dot 2 dot 1.
Our next step is to implement source net.
And that's so that when these clients eventually, once we build the segment and
the tier 1 gateway,
when their traffic hits the tier zero, we want to go ahead and net it over.
And so for a game plan, let's net all the traffic here to 23 dot 1 dot 2 dot 60 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so for a game plan, let's net all the traffic here to 23 dot 1 dot 2 dot 60
.
Let's imagine that's an IP address that we're allowed to use here between us
and our service
provider and for site two, let's use 24 dot 1 dot 2 dot 60 as the net address.
And for conditions, we'll say anybody coming in from the source address of 10,
anything,
go ahead and do that same thing for this net rule here.
So once again, we're taking this common stretched tier zero gateway and we're
creating two net
rules, one that would be used if traffic is going out through service provider
A over here at site one, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
A over here at site one,
and one that would be used if traffic is going out through service provider B
through site two.
So once again, we'll go back to our global manager and let's create our two net
rules.
So back at the global manager, what we'll do is on the left, we're going to go
down to
net under network services. And then here, the main pane, if we had multiple T
zero gateways,
we could choose when we went to apply it to. So we only have one stretched T
zero gateway,
and that's the one right here. So let's like it. And then we'll click right
here and add net rule.
So we'll click on add net rule, and let's go ahead and collapse the left hand WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll click on add net rule, and let's go ahead and collapse the left hand
column to give us a
little more room. And I'll call it a site one s net. And then the type is going
to be source net.
And then for the source IP address field right here, let's say any traffic that
is source from
10, anything. So we'll put 10 zero zero zero slash eight to represent we only
care about matching on
that first octet, the 10. And that way, if we have additional subnets under the
10 network,
those will be matched by this rule. And then let's also specify the translated
IP address we want to
use, which based on our plan was 23 dot 1 dot 2 dot 60. And then this becomes
super important WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
super important
here. We want to go ahead and apply this only to the interfaces associated with
site one. So in
the apply to column here, we'll click on set. And then with site one selected,
let's go ahead and
choose the interfaces where we want to apply this. Now we could say apply rule
to all entities of
a selected site. However, as we get to the DHCP section, I'm going to create an
additional
interface where I don't want to use net on that interface. So I'm going to say
don't apply it to
everywhere, but do apply it to these two interfaces, which are at site one. So
with those two interfaces WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with those two interfaces
selected, we'll click on apply, then we'll scroll down, click on save. And now
we have this new site
one source net rule, and we'll create a similar rule for the benefit of site
two, except for the
translated address, we'll choose the 24 dot 1 dot 2 dot 60, instead of 23. And
for the applies to,
we'll choose the two interfaces associated with site two. So we'll click on add
net rule,
we'll call it site two source net. And for the type, we want to do source net.
And for the source
IP address, we'll use the same condition and a source traffic starting with 10, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
IP address, we'll use the same condition and a source traffic starting with 10,
anything would
qualify. And for the translated address, we're use 24 dot 1 dot 2 dot 60. And
then we want to use
the apply to column here, click on set. And we want to associate this with the
two interfaces
over at site two. So with site two selected, we'll go ahead and choose those
two interfaces,
and click on apply, and we'll scroll down and click on save. All right, so now
we have two
source net rules, one for site one, one for site two. So any traffic source
from 10, anything that's
going up to the internet, if it's going through site one out through service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
going up to the internet, if it's going through site one out through service
provider A, it's
going to be natted to this address. And if it's going out to the internet
through site two,
it's going to be natted to 24 dot 1 dot 2 dot 60. So in our journey, we are at
this point right
here, we have the t zero created, we have the external interfaces on each site
associated with
that t zero gateway, we set up static default routes at site one and site two
with their respective
service providers. And we also set up source net rules for both site one and
site two. So our
next step in the journey is then to go ahead and create the stretch t one that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
next step in the journey is then to go ahead and create the stretch t one that
's connected to the
t zero, we'll also go ahead and create this segment right here. And we get to
do that configuration of
adding this t zero gateway in the next video. So I'll see you there in just a
moment.