WEBVTT 1 00:00.000 --> 00:04.400 So let's imagine the customer, they started the NAP automation, they did that 2 00:04.400 --> 00:04.960 by deploying 3 00:04.960 --> 00:09.480 the automation VM, making sure they had the plug in here as part of the NSX 4 00:09.480 --> 00:10.080 manager, 5 00:10.080 --> 00:14.000 and then as they were going through, it stopped working. So let's consider 6 00:14.000 --> 00:14.640 together some of the 7 00:14.640 --> 00:17.890 recommendations that we would have for them. One of our first recommendations 8 00:17.890 --> 00:19.280 would be to check 9 00:19.280 --> 00:25.090 the basic functionality of the network where they're deploying the NAP, 10 00:25.090 --> 00:26.560 including making sure they 11 00:26.560 --> 00:31.480 have correct name resolution from any devices on these network segments for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:26.560 --> 00:31.480 have correct name resolution from any devices on these network segments for 12 00:31.480 --> 00:32.880 both internal resources 13 00:32.880 --> 00:37.140 like the vCenter server appliance and the NSX manager, and also making sure 14 00:37.140 --> 00:38.160 that the devices 15 00:38.160 --> 00:42.120 on these networks can actually get up to the internet. Also, if they have any 16 00:42.120 --> 00:43.040 type of firewall 17 00:43.040 --> 00:46.840 and restrictions between these various network segments, they'd want to make 18 00:46.840 --> 00:47.600 sure that based 19 00:47.600 --> 00:50.800 on the prereqs for the deployment that they are permitting the required 20 00:50.800 --> 00:52.480 protocols, ports, and services. 21 00:52.480 --> 00:56.310 So let's presume that we help them in verifying all of that and their network 22 00:56.310 --> 00:57.520 infrastructure was 23 00:57.520 --> 01:01.580 solid. Additional things to check would be to verify that on the cluster where WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:57.520 --> 01:01.580 solid. Additional things to check would be to verify that on the cluster where 24 01:01.580 --> 01:02.560 they're going to be 25 01:02.560 --> 01:07.180 deploying the NAP, we'd want to make sure that that cluster is already set up 26 01:07.180 --> 01:10.000 for HA and DRS. 27 01:10.000 --> 01:14.260 Because when we deployed initially, it went out and checked and enabled HA on 28 01:14.260 --> 01:15.280 that cluster, 29 01:15.280 --> 01:19.140 but then when I went to deploy the VM, the HA proxy, I don't think the HA 30 01:19.140 --> 01:20.160 cluster was quite 31 01:20.160 --> 01:23.880 fully baked and ready and ready to go. And so then when we went back to the 32 01:23.880 --> 01:24.960 wizard and we reset 33 01:24.960 --> 01:29.050 everything, we went through it again, because the HA and the DRS was already 34 01:29.050 --> 01:30.480 set up and functioning, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:29.050 --> 01:30.480 set up and functioning, 35 01:30.480 --> 01:34.600 it's at that point it was able to deploy the HA proxy. Now it may not just be 36 01:34.600 --> 01:35.520 at the HA proxy 37 01:35.520 --> 01:39.160 where we have a problem or an issue, it could be at any one of the steps in the 38 01:39.160 --> 01:40.240 deployment process. 39 01:40.240 --> 01:43.740 So the key would be to identify where it failed, and then go back and look at 40 01:43.740 --> 01:44.880 the resources available, 41 01:44.880 --> 01:49.670 whether they're log files or recent events or the events inside of vSphere to 42 01:49.670 --> 01:50.640 see exactly what 43 01:50.640 --> 01:54.550 failed, resolve that problem, and then move forward and continue on to the next 44 01:54.550 --> 01:55.600 step. And we may have 45 01:55.600 --> 02:00.080 to rerun that wizard as part of the automation VM, we may have to run that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 01:55.600 --> 02:00.080 to rerun that wizard as part of the automation VM, we may have to run that 46 02:00.080 --> 02:01.520 multiple times. As we 47 02:01.520 --> 02:05.360 identify problems, correct them, and then continue to move forward. So our end 48 02:05.360 --> 02:06.320 goal is to make sure 49 02:06.320 --> 02:10.840 that the NSX application platform is fully deployed, and then we can start 50 02:10.840 --> 02:12.320 using it once it's ready. 51 02:12.320 --> 02:16.090 So thanks for joining me in this set of videos regarding using the NAP 52 02:16.090 --> 02:17.360 automation. And now that 53 02:17.360 --> 02:21.890 we have this NSX application platform in our environment, in the next skill, we 54 02:21.890 --> 02:22.480 'll take a look 55 02:22.480 --> 02:27.140 at how do we actually use the NSX application platform that's now been deployed 56 02:27.140 --> 02:28.160 . So I'll see you 57 02:28.160 --> 02:31.670 soon for that next set of videos. Until then, I hope this has been informative WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 02:28.160 --> 02:31.670 soon for that next set of videos. Until then, I hope this has been informative 58 02:31.670 --> 02:32.640 and I'd like to. 59 02:32.640 --> 02:39.280 Thank you for viewing.