WEBVTT 1 00:00.210 --> 00:01.380 So, let's compare notes 2 00:01.380 --> 00:02.970 regarding some suggestions, 3 00:02.970 --> 00:04.380 regarding what the customer 4 00:04.380 --> 00:05.760 may be experiencing 5 00:05.760 --> 00:08.130 and how to fix their problem with VMs. 6 00:08.130 --> 00:10.680 For example, on one subnet like 10.10.0 7 00:10.680 --> 00:11.513 not being able to communicate 8 00:11.513 --> 00:12.346 with other VMs 9 00:12.346 --> 00:14.040 on different subnets 10 00:14.040 --> 00:15.270 like 10.20.0. 11 00:15.270 --> 00:16.260 So, what are the elements 12 00:16.260 --> 00:17.340 at the VM level, 13 00:17.340 --> 00:19.110 at the client level could be, 14 00:19.110 --> 00:22.200 is there default gateway configured correctly? 15 00:22.200 --> 00:24.630 Meaning do they have a default gateway 16 00:24.630 --> 00:26.520 that points to a valid IP address? 17 00:26.520 --> 00:28.500 So, on these routers right here, 18 00:28.500 --> 00:29.940 these tier one gateways, 19 00:29.940 --> 00:30.967 if we're using .1 here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 00:29.940 --> 00:30.967 if we're using .1 here 20 00:30.967 --> 00:32.673 on the 10.10.0.1 network, 21 00:32.673 --> 00:34.500 we wanna make sure that our clients on 22 00:34.500 --> 00:36.770 that subnet are also using that IP address 23 00:36.770 --> 00:39.540 10.10.0.1 as their default gateway. 24 00:39.540 --> 00:41.340 So maybe they're DHCP clients, 25 00:41.340 --> 00:43.020 or statically configured, 26 00:43.020 --> 00:45.750 we'd wanna make sure that we had that IP address there 27 00:45.750 --> 00:46.800 and that our VMs were 28 00:46.800 --> 00:48.570 using the appropriate default gateway. 29 00:48.570 --> 00:49.680 So up here for gateway 30 00:49.680 --> 00:51.510 is it correctly configured on the segment 31 00:51.510 --> 00:53.040 where the gateway is connected? 32 00:53.040 --> 00:56.085 And also is it correct in the configuration on the VMs? 33 00:56.085 --> 00:58.980 Another challenge for inter VLAN communications could come 34 00:58.980 --> 01:02.730 up if our tier one gateways are not advertising their WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 00:58.980 --> 01:02.730 up if our tier one gateways are not advertising their 35 01:02.730 --> 01:05.610 directly connected networks up to the tier zero. 36 01:05.610 --> 01:08.670 So if gateway A doesn't advertise that 10.10 37 01:08.670 --> 01:11.850 that it's connected, and Gateway B doesn't advertise 38 01:11.850 --> 01:13.590 that 10.20 is connected, 39 01:13.590 --> 01:16.140 that would prevent this tier zero router 40 01:16.140 --> 01:18.960 from being able to forward packets beyond that point 41 01:18.960 --> 01:20.520 for those respective subnets. 42 01:20.520 --> 01:22.530 So, here I'll say are the tier ones 43 01:22.530 --> 01:24.690 advertising connected networks, 44 01:24.690 --> 01:27.540 and in the event one of these VMs on the 10.10 45 01:27.540 --> 01:31.050 or 10.20 networks can't communicate with other VMs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 01:27.540 --> 01:31.050 or 10.20 networks can't communicate with other VMs 46 01:31.050 --> 01:32.760 on another ES6i host, 47 01:32.760 --> 01:34.380 perhaps there's something incorrect 48 01:34.380 --> 01:35.940 with the transport network. 49 01:35.940 --> 01:37.740 Maybe on the transport network we have a routing 50 01:37.740 --> 01:40.320 or a switching problem that's preventing the forwarding 51 01:40.320 --> 01:43.380 of the tunnel traffic between ES6i hosts. 52 01:43.380 --> 01:45.300 So that could be yet another challenge 53 01:45.300 --> 01:47.490 preventing basic communication 54 01:47.490 --> 01:50.670 from any VMs on any subnets on ES6i-A 55 01:50.670 --> 01:52.590 going over to any VMs on any subnets 56 01:52.590 --> 01:54.420 over here on ESXi-B. 57 01:54.420 --> 01:55.290 So I'll make a note here 58 01:55.290 --> 01:56.760 it could be the transport network. 59 01:56.760 --> 01:57.960 And regarding the transport network, 60 01:57.960 --> 02:00.251 that also implies the uplink profiles WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 60 01:57.960 --> 02:00.251 that also implies the uplink profiles 61 02:00.251 --> 02:02.370 that the transport nodes are using 62 02:02.370 --> 02:04.950 are using the correct physical uplinks 63 02:04.950 --> 02:06.120 on their respective hosts. 64 02:06.120 --> 02:08.220 And again, any problem with the transport network could 65 02:08.220 --> 02:10.110 cause problems between VMs on one host 66 02:10.110 --> 02:11.550 and VMs on another host. 67 02:11.550 --> 02:13.380 So that's a fantastic starting point 68 02:13.380 --> 02:15.690 and also if there were firewall rules 69 02:15.690 --> 02:18.090 and gateway rules that are set up for protecting 70 02:18.090 --> 02:20.100 and controlling traffic flows, that could be 71 02:20.100 --> 02:22.020 yet another area to look at, 72 02:22.020 --> 02:24.120 but we haven't covered any kind of firewalls 73 02:24.120 --> 02:25.740 or security policy rules yet. 74 02:25.740 --> 02:27.180 So assuming we're using the defaults 75 02:27.180 --> 02:28.860 where we're allowing all traffic, 76 02:28.860 --> 02:30.870 that wouldn't be an issue at this stage in the game. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 02:28.860 --> 02:30.870 that wouldn't be an issue at this stage in the game. 77 02:30.870 --> 02:32.700 So, thanks for joining me in this section 78 02:32.700 --> 02:34.290 of our skill regarding validating 79 02:34.290 --> 02:35.640 and reinforcing our knowledge, 80 02:35.640 --> 02:36.990 and I'll see you, my friend, 81 02:36.990 --> 02:38.940 in the next skill when you are ready. 82 02:38.940 --> 02:41.370 Until then, I hope this has been informative 83 02:41.370 --> 02:43.863 and I'd like to thank you for viewing.