So, let's compare notes
regarding some suggestions,
regarding what the customer
may be experiencing
and how to fix their problem with VMs.
For example, on one subnet like 10.10.0
not being able to communicate
with other VMs
on different subnets
like 10.20.0.
So, what are the elements
at the VM level,
at the client level could be,
is there default gateway configured correctly?
Meaning do they have a default gateway
that points to a valid IP address?
So, on these routers right here,
these tier one gateways,
if we're using .1 here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if we're using .1 here
on the 10.10.0.1 network,
we wanna make sure that our clients on
that subnet are also using that IP address
10.10.0.1 as their default gateway.
So maybe they're DHCP clients,
or statically configured,
we'd wanna make sure that we had that IP address there
and that our VMs were
using the appropriate default gateway.
So up here for gateway
is it correctly configured on the segment
where the gateway is connected?
And also is it correct in the configuration on the VMs?
Another challenge for inter VLAN communications could come
up if our tier one gateways are not advertising their WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
up if our tier one gateways are not advertising their
directly connected networks up to the tier zero.
So if gateway A doesn't advertise that 10.10
that it's connected, and Gateway B doesn't advertise
that 10.20 is connected,
that would prevent this tier zero router
from being able to forward packets beyond that point
for those respective subnets.
So, here I'll say are the tier ones
advertising connected networks,
and in the event one of these VMs on the 10.10
or 10.20 networks can't communicate with other VMs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or 10.20 networks can't communicate with other VMs
on another ES6i host,
perhaps there's something incorrect
with the transport network.
Maybe on the transport network we have a routing
or a switching problem that's preventing the forwarding
of the tunnel traffic between ES6i hosts.
So that could be yet another challenge
preventing basic communication
from any VMs on any subnets on ES6i-A
going over to any VMs on any subnets
over here on ESXi-B.
So I'll make a note here
it could be the transport network.
And regarding the transport network,
that also implies the uplink profiles WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that also implies the uplink profiles
that the transport nodes are using
are using the correct physical uplinks
on their respective hosts.
And again, any problem with the transport network could
cause problems between VMs on one host
and VMs on another host.
So that's a fantastic starting point
and also if there were firewall rules
and gateway rules that are set up for protecting
and controlling traffic flows, that could be
yet another area to look at,
but we haven't covered any kind of firewalls
or security policy rules yet.
So assuming we're using the defaults
where we're allowing all traffic,
that wouldn't be an issue at this stage in the game. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that wouldn't be an issue at this stage in the game.
So, thanks for joining me in this section
of our skill regarding validating
and reinforcing our knowledge,
and I'll see you, my friend,
in the next skill when you are ready.
Until then, I hope this has been informative
and I'd like to thank you for viewing.