Hello and welcome.
My name is Keith Barker.
And up to this point, we've been focusing primarily
on the concept of the distributed router inside of NSX
that can provide the routing for east west traffic
also with a tier-0 and a couple tier-1 gateways.
We could also route all the way through them
from VMs on one segment over to another.
And one of the really cool things
about a distributed router, a DR,
is that it can exist
on all of our transport nodes that need to have it.
For example, ESXiA and ESXiB, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
For example, ESXiA and ESXiB,
they've got the distributed router component.
Our edge devices,
they have copies of that distributed router
for T0 and a couple T1s.
And again, up to this point,
that's been our primary focus
about working with and configuring
and then verifying those distributed routers.
However, there comes a time in every network's life
when we need to have some other services.
For example, we may wanna set up network address translation
at one of our tier-0 gateways.
And for those network services,
including network address translations,
stateful firewall, and VPNs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
stateful firewall, and VPNs,
we need an additional component
on those devices providing those services,
and that extra component
for those additional network services
is referred to as a services router.
So think of the distributed router
as the routing information on how to get places
and how to forward traffic.
And we can think of the services router component,
even if it's on the same logical router,
we can give the services router as the component
that's gonna provide those services.
For example, provide network address translation
or provide VPN services or a gateway based firewall. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or provide VPN services or a gateway based firewall.
Another time the services router comes into play
is if we're gonna be accessing
the actual physical external network.
So we may have VMs down here in our segments,
and they wanna be able to route
with east-west traffic, no problem,
but also, they may need to get access
out to the physical network in our topology
or beyond that to the internet.
And anytime we're gonna bridge our NSX routed environment
with a physical environment,
that also is going to invoke a services router function
on that router, on that gateway
that's providing that service
from the logical NSX routed environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
from the logical NSX routed environment
over to the physical network.
So in this guild, we're gonna do this.
We're gonna take our existing topology,
which currently has three routers,
two tier-1s and one tier-0,
and at the tier-0,
we are going to add on top of its responsibilities,
connections out to the physical network
on behalf of the internal routed environment.
That way a VM like VM1, if it needs to or wants to,
can get access not just to the NSX routed networks,
but also out to the physical network as well.
And, again, to do that,
when we add that additional functionality
for connectivity or bridging out to the physical network, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for connectivity or bridging out to the physical network,
that is going to require a services router component
inside of our NSX.
So join me in the next video
as we take a big picture look at our overall process,
we'll follow it up with a game plan,
and then what you and I get to do
is both implement and verify as we go.
So I'll see you, my friend, in the very next video.