WEBVTT 00:00:00.000 --> 00:00:08.000 Welcome back to vSphere 8 in the real world, and now we're going to discuss the VCSA upgrade process. 00:00:08.000 --> 00:00:16.000 So the VCSA is the vCenter's virtual appliance that VMware has been deploying for a while now. 00:00:16.000 --> 00:00:24.000 When we first started with VMware back in the 3.5 days or before that, 3.0, 3.5, and then going forward, 00:00:24.000 --> 00:00:26.000 vCenter was installed on a Windows machine. 00:00:26.000 --> 00:00:30.000 So we'd have a Windows machine, and we would install vCenter on that Windows machine. 00:00:30.000 --> 00:00:36.000 It could be a virtual Windows machine, or it could be a physical Windows box that was in our environment, 00:00:36.000 --> 00:00:38.000 but it was installed on Windows. 00:00:38.000 --> 00:00:45.000 Then VMware came out with that virtual appliance, and when it first, first came out, it was kind of touted as 00:00:45.000 --> 00:00:49.000 a quick way to deploy vCenter for like a lab environment or something like that. 00:00:49.000 --> 00:00:54.000 And then quickly VMware started saying, this is the way to deploy vCenter in production, 00:00:54.000 --> 00:00:56.000 and then it became, this is the only way to deploy vCenter. 00:00:56.000 --> 00:01:00.000 So for a long time, you had the choice between, or for quite a while anyway, 00:01:00.000 --> 00:01:03.000 you had the choice between the virtual appliance or deploying it on Windows. 00:01:03.000 --> 00:01:12.000 Now it's just a virtual appliance, and migrating away from a Windows version of the vCenter to the virtual appliance 00:01:12.000 --> 00:01:17.000 version is not super difficult, but it is a process. 00:01:17.000 --> 00:01:19.000 There are steps involved, and we'll discuss that as we go forward. 00:01:19.000 --> 00:01:28.000 So when we do a vSphere upgrade, meaning we're going to upgrade from one version of, you know, vSphere to another. 00:01:28.000 --> 00:01:31.000 So we are on 7, and we want to go to 8, for example. 00:01:31.000 --> 00:01:38.000 We do more than just upgrade vCenter, but the first thing we're going to upgrade is we're going to upgrade vCenter. 00:01:38.000 --> 00:01:41.000 After we've upgraded vCenter, then we're going to upgrade our ESXi host. 00:01:41.000 --> 00:01:48.000 After we've upgraded our ESXi host, then we can upgrade the VMs, meaning the virtual hardware on the VMs 00:01:48.000 --> 00:01:51.000 that they're running, and then we can upgrade VMware tools. 00:01:51.000 --> 00:01:57.000 You don't want to upgrade out of that order, okay? 00:01:57.000 --> 00:02:02.000 You don't want to start up trying to upgrade your ESXi host before vCenter because the new host, 00:02:02.000 --> 00:02:05.000 the newer version of the host, aren't going to work with an old version of vCenter. 00:02:05.000 --> 00:02:09.000 You need to have the most current version of vCenter, which works with older hosts. 00:02:09.000 --> 00:02:14.000 Then you can upgrade your older host to the current version that matches your vCenter. 00:02:15.000 --> 00:02:21.000 Then we can upgrade the VMs virtual hardware because now the new ESXi host can understand that new virtual hardware. 00:02:21.000 --> 00:02:26.000 Then we can upgrade the VMware tools because that will give us all that additional functionality then. 00:02:26.000 --> 00:02:29.000 So that's the order you need to make sure you do that. 00:02:29.000 --> 00:02:33.000 If you're going to do an upgrade in your environment, okay, we're on 7 and 8's out. 00:02:33.000 --> 00:02:35.000 We want to upgrade to 8. 00:02:35.000 --> 00:02:37.000 First, you do vCenter. 00:02:37.000 --> 00:02:38.000 Then you do your hosts. 00:02:38.000 --> 00:02:40.000 Then you do your VMs virtual hardware. 00:02:40.000 --> 00:02:42.000 Then you do your VMware tools. 00:02:42.000 --> 00:02:45.000 It's very important you do them in that order, vCenter first, hosts second. 00:02:47.000 --> 00:02:49.000 Now, what can we upgrade from and to? 00:02:49.000 --> 00:02:54.000 We can go from 6.5 or 6.7 to 7, and we can go from 7 to 8. 00:02:54.000 --> 00:02:57.000 We can't go from 6.7 straight to 8. 00:02:57.000 --> 00:03:03.000 If we are on 6.5 or 6.7 and we want to go to 8, we have to do a multi-hop upgrade. 00:03:03.000 --> 00:03:05.000 We need to go to 7. 00:03:05.000 --> 00:03:07.000 Then we can go to 8. 00:03:07.000 --> 00:03:10.000 You're going to have to do your upgrade twice in that scenario. 00:03:12.000 --> 00:03:18.000 Now, if you're on an older 6.7 vCenter, actually you're going to have several different pieces. 00:03:18.000 --> 00:03:21.000 You're going to have the vCenter server service. 00:03:21.000 --> 00:03:26.000 You're going to have the PSC, which is how you do your authentication and things like that, 00:03:26.000 --> 00:03:28.000 your platform service controller. 00:03:28.000 --> 00:03:30.000 And then you're going to have, of course, the operating system, 00:03:30.000 --> 00:03:33.000 which is going to be Linux on the virtual appliance. 00:03:33.000 --> 00:03:36.000 When we're done, we're going to have vCenter. 00:03:36.000 --> 00:03:38.000 vCenter is going to include all the components. 00:03:39.000 --> 00:03:45.000 If we go back to 5, 5 could be broken out into as many as I believe it was like six different virtual machines. 00:03:45.000 --> 00:03:51.000 And so all these different services could be broken out into all these different virtual machines spread out, 00:03:51.000 --> 00:03:53.000 and then we had to tie them all together. 00:03:53.000 --> 00:03:55.000 It was very complicated. 00:03:55.000 --> 00:04:00.000 And you could put them all down onto one, but you would often see people trying to get fancy 00:04:00.000 --> 00:04:04.000 and put them in different ones, and you'd get corruption, and it was a huge, huge mess. 00:04:05.000 --> 00:04:09.000 VMware consolidated that down, so now it's only two pieces. 00:04:09.000 --> 00:04:12.000 And then with 7, now it's only one piece. 00:04:12.000 --> 00:04:13.000 And 8, it's one. 00:04:13.000 --> 00:04:15.000 It's one vCenter. 00:04:15.000 --> 00:04:17.000 And vCenter runs all the different services, 00:04:17.000 --> 00:04:23.000 and we no longer have an external single sign-on component that we need to try and manage separately 00:04:23.000 --> 00:04:24.000 and things like that. 00:04:24.000 --> 00:04:26.000 It's all integrated into it. 00:04:26.000 --> 00:04:28.000 We have a single sign-on module, but it's an internal. 00:04:28.000 --> 00:04:34.000 We don't have the external one that you could deploy separately. 00:04:34.000 --> 00:04:36.000 So upgrades, what will you need? 00:04:36.000 --> 00:04:41.000 So obviously if you're going to upgrade from 6, 7, you'll have your platform service controller, right, 00:04:41.000 --> 00:04:43.000 where you need to upgrade that. 00:04:43.000 --> 00:04:46.000 We're going to upgrade the vCenter server appliance itself, 00:04:46.000 --> 00:04:49.000 and verification the system meets the minimum requirements for updating. 00:04:49.000 --> 00:04:53.000 So, again, if we're going from 6, 7, we're not going to go to 8, right? 00:04:53.000 --> 00:04:56.000 Going from 6, 7, we're going to go to 7, and then 7, we're going to go to 8. 00:04:56.000 --> 00:04:58.000 All right. 00:04:58.000 --> 00:05:01.000 So when you install, you can install two different ways. 00:05:01.000 --> 00:05:03.000 You can upgrade two different ways. 00:05:03.000 --> 00:05:06.000 You can do it from the GUI, or you can do it from the CLI. 00:05:06.000 --> 00:05:09.000 You might do it from the CLI if you wanted to, like, automate this. 00:05:09.000 --> 00:05:11.000 You don't want to sit there and click next, next, next. 00:05:11.000 --> 00:05:14.000 If you're doing one, if you have one vCenter in your environment, 00:05:14.000 --> 00:05:19.000 you're probably just going to go through the GUI and just, you know, answer the questions and go through it. 00:05:19.000 --> 00:05:24.000 It's not really worth it to create a long customization answer file or script. 00:05:25.000 --> 00:05:28.000 And if you're not going to do that, there's not a lot of reason to do it from the CLI. 00:05:28.000 --> 00:05:29.000 You could. 00:05:29.000 --> 00:05:30.000 You could. 00:05:30.000 --> 00:05:34.000 But most of the time, you do it from the CLI because you want to automate things, right? 00:05:34.000 --> 00:05:39.000 You could go through the CLI and, you know, but usually if you're only doing one, 00:05:39.000 --> 00:05:42.000 you're going to do the GUI, and you're just going to answer the questions along the way. 00:05:42.000 --> 00:05:48.000 If I have a huge infrastructure, and my huge infrastructure has a lot of vCenter servers, 00:05:48.000 --> 00:05:52.000 and I want to automate the process of updating all these different vCenter servers 00:05:52.000 --> 00:05:56.000 in this big infrastructure I have, then we might look at using the CLI 00:05:56.000 --> 00:06:01.000 and creating some answer files and scripting the upgrade process. 00:06:01.000 --> 00:06:06.000 But for one, maybe two, you probably aren't going to do that. 00:06:06.000 --> 00:06:09.000 So upgrade the vCenter server appliance, right? 00:06:09.000 --> 00:06:12.000 Does the equipment meet the upgrade requirements? 00:06:12.000 --> 00:06:16.000 So do we have the right hardware and things like that in place to do this upgrade? 00:06:16.000 --> 00:06:18.000 Prepare your network for the upgrade. 00:06:18.000 --> 00:06:19.000 Firewall ports. 00:06:19.000 --> 00:06:23.000 We'll go over just a moment all the different services that vCenter uses, 00:06:23.000 --> 00:06:26.000 and we want to make sure if we have a network that's segmented 00:06:26.000 --> 00:06:29.000 and we only allow a zero-trust communication through, 00:06:29.000 --> 00:06:32.000 so we only allow just the ports needed, 00:06:32.000 --> 00:06:34.000 then we'll need to make sure we have all the right ports open, 00:06:34.000 --> 00:06:37.000 and we'll go over those in a moment. 00:06:37.000 --> 00:06:41.000 Upgrade or migrate the appliance in the GUI or the CLI. 00:06:41.000 --> 00:06:42.000 How are we going to do that? 00:06:42.000 --> 00:06:44.000 So probably you're going to go to the GUI most of the time. 00:06:44.000 --> 00:06:47.000 Most people do from the GUI. 00:06:47.000 --> 00:06:48.000 You'll go to the wizard. 00:06:48.000 --> 00:06:52.000 It'll be a couple-of-step process, and then you'll be finished 00:06:52.000 --> 00:06:57.000 and you'll do your post-upgrade work and you'll be all done. 00:06:57.000 --> 00:07:00.000 So here we're looking at some hardware requirements, right? 00:07:00.000 --> 00:07:06.000 So if we need a small, tiny environment, like we have no more than 10 hosts 00:07:06.000 --> 00:07:09.000 and no more than 100 VMs, so this is probably maybe a lab or something like that, 00:07:09.000 --> 00:07:12.000 or maybe it's a small business running it. 00:07:12.000 --> 00:07:14.000 Minimum hardware, two virtual CPUs, 12 gigs of RAM. 00:07:14.000 --> 00:07:19.000 That kind of is really like the minimum you want on that environment. 00:07:19.000 --> 00:07:22.000 Small, 100 hosts and 1,000 VMs. 00:07:22.000 --> 00:07:24.000 For some of you that might not seem that small, 00:07:24.000 --> 00:07:27.000 but for a big enterprise that would be obviously considered small. 00:07:27.000 --> 00:07:30.000 Four virtual CPUs, 19 gigs of RAM. 00:07:30.000 --> 00:07:35.000 Medium, 404,000, so eight virtual CPUs, 128 gigs of RAM. 00:07:35.000 --> 00:07:41.000 You kind of see as we go through here, we end with 2,000 hosts, 35,000 VMs. 00:07:42.000 --> 00:07:45.000 We need 24 virtual CPUs and 56 gigs of RAM. 00:07:45.000 --> 00:07:49.000 So that starts to get – I mean, the 24 CPUs is more daunting 00:07:49.000 --> 00:07:53.000 than the 56 gigs of RAM part is for a lot of people. 00:07:53.000 --> 00:07:55.000 That's an extra-large environment. 00:07:55.000 --> 00:07:57.000 Now, what if you need more than 2,000 hosts? 00:07:57.000 --> 00:08:00.000 What if you have more than 35,000 VMs? 00:08:00.000 --> 00:08:03.000 Then what you're going to need to do is deploy another vCenter server 00:08:03.000 --> 00:08:09.000 and you'll use them in linked mode probably. 00:08:09.000 --> 00:08:15.000 For storage, for tiny, the default is 415 gigabytes. 00:08:15.000 --> 00:08:21.000 Now, do we want to do an environment where we have a small – 00:08:21.000 --> 00:08:24.000 it's a small appliance, but we want a large amount of space 00:08:24.000 --> 00:08:26.000 or an extra-large amount of space? 00:08:26.000 --> 00:08:28.000 We want to do a lot of logging. 00:08:28.000 --> 00:08:30.000 We're doing a small appliance, we want to do a lot of logging. 00:08:30.000 --> 00:08:34.000 Then you might want to start incrementing the amount of disk space you're using. 00:08:34.000 --> 00:08:37.000 As you can see, we could go as high as an extra-large, 00:08:37.000 --> 00:08:43.000 which requires the default 1,805 gigabytes of disk space. 00:08:43.000 --> 00:08:47.000 But if we want to log additional, we might go into 1905 00:08:47.000 --> 00:08:51.000 all the way up to 3,665 gigs of space. 00:08:51.000 --> 00:08:53.000 That means we're going to be storing a lot of logs. 00:08:53.000 --> 00:08:57.000 If you're doing a lot of logging and you think you might need a lot of disk space, 00:08:57.000 --> 00:09:00.000 you probably want a syslog server to help gather that and sort through 00:09:00.000 --> 00:09:03.000 and make sense of it and create alerts for you and things like that. 00:09:03.000 --> 00:09:08.000 You're storing a huge amount of log information for not a lot of reason. 00:09:08.000 --> 00:09:10.000 Software. 00:09:10.000 --> 00:09:13.000 Again, you can run it from the GUI or the CLI. 00:09:13.000 --> 00:09:16.000 You can run it from Windows, Linux, or a Mac. 00:09:16.000 --> 00:09:19.000 And here it shows you if you're running on Linux, 00:09:19.000 --> 00:09:21.000 the different versions of Linux that are supported 00:09:21.000 --> 00:09:22.000 and the minimum hardware. 00:09:22.000 --> 00:09:24.000 Windows, if you want to run it from Windows, 00:09:24.000 --> 00:09:27.000 here's a version of Windows, Windows 8, 8.1, 10, 00:09:27.000 --> 00:09:30.000 the different versions of Windows Server, 2012, 16, 19, 00:09:31.000 --> 00:09:34.000 and then the minimum hardware for that Windows box to run the installer, 00:09:34.000 --> 00:09:37.000 and then it has all the Mac information, too. 00:09:37.000 --> 00:09:39.000 So pretty minimal, right? 00:09:39.000 --> 00:09:42.000 It supports most versions of Windows that you'll see out there in the field 00:09:42.000 --> 00:09:45.000 nowadays, and the hardware requirements aren't that much. 00:09:45.000 --> 00:09:48.000 The installer's not super heavy duty. 00:09:48.000 --> 00:09:50.000 A lot of the work, once it gets started deploying, 00:09:50.000 --> 00:09:52.000 the actual work's done on the host. 00:09:52.000 --> 00:09:54.000 That's actually creating the virtual appliance 00:09:54.000 --> 00:09:56.000 and running the virtual appliance, not the virtual machine 00:09:56.000 --> 00:09:59.000 that's pushing out the installer. 00:09:59.000 --> 00:10:02.000 So here we're seeing the network ports, right? 00:10:02.000 --> 00:10:06.000 So, for example, you probably want to have SSH access, which is port 22. 00:10:06.000 --> 00:10:11.000 DNS access, which is going to be UDP-53 for queries, 00:10:11.000 --> 00:10:14.000 and if you're doing some kind of DNS replication, that's TCP, 00:10:14.000 --> 00:10:19.000 but the ESXi host will be doing queries, so UDP port 53. 00:10:19.000 --> 00:10:25.000 AD for HTTP, 88 for active directory servers for authentication. 00:10:25.000 --> 00:10:28.000 And we can kind of go down this line, LDAP, HTTPS, 00:10:28.000 --> 00:10:30.000 are we using syslog servers? 00:10:30.000 --> 00:10:33.000 Usually it's considered a good idea. 00:10:33.000 --> 00:10:39.000 RPC, remote procedure call ports, all the way through to the vSphere client 00:10:39.000 --> 00:10:42.000 uses HTTPS on port 9443. 00:10:42.000 --> 00:10:46.000 So all these ports are going to need to be configured to allow for your 00:10:46.000 --> 00:10:50.000 firewall if you are, you know, segmenting your network 00:10:50.000 --> 00:10:52.000 in a zero-trust type environment. 00:10:52.000 --> 00:10:55.000 If you're not, if you just have simple routing and everything's wide open, 00:10:55.000 --> 00:11:00.000 then these ports won't be as important for you to know. 00:11:00.000 --> 00:11:02.000 So DNS is required, okay? 00:11:02.000 --> 00:11:06.000 So when you go to deploy vCenter, the vCenter server needs to be, 00:11:06.000 --> 00:11:11.000 have its name, whatever name you assign to the vCenter server 00:11:11.000 --> 00:11:14.000 and whatever IP address you give the vCenter server need to be registered 00:11:14.000 --> 00:11:16.000 with an A record in DNS. 00:11:16.000 --> 00:11:20.000 So DNS needs to have that registered in there because the installer is going 00:11:20.000 --> 00:11:22.000 to go through and query that and make sure it's there 00:11:22.000 --> 00:11:23.000 and make sure it resolves properly. 00:11:23.000 --> 00:11:27.000 And if it doesn't resolve properly, then the installation is going to fail. 00:11:27.000 --> 00:11:32.000 So make sure that you do have, you know, records configured in DNS 00:11:32.000 --> 00:11:34.000 that match the name you assigned the vCenter server 00:11:34.000 --> 00:11:36.000 and the IP address you're going to give it. 00:11:36.000 --> 00:11:41.000 So plan that in advance and make sure that's in DNS. 00:11:41.000 --> 00:11:45.000 So, again, we need to have, you know, our A record that, you know, 00:11:45.000 --> 00:11:47.000 resolves to an IPv4 address, right? 00:11:47.000 --> 00:11:52.000 You can verify that using your NS lookup tool from the command line. 00:11:52.000 --> 00:11:53.000 Clock synchronization. 00:11:53.000 --> 00:11:56.000 You're going to see this come up multiple times in this lesson. 00:11:56.000 --> 00:12:00.000 So clock synchronization is super important because authentication is going 00:12:00.000 --> 00:12:03.000 to be super important, right? 00:12:03.000 --> 00:12:07.000 So SSL certificates need to have, you know, the timing be within a few minutes. 00:12:07.000 --> 00:12:10.000 SAML tokens need their timing to be within five minutes. 00:12:10.000 --> 00:12:13.000 So both of them are going to be very time sensitive. 00:12:13.000 --> 00:12:16.000 So clock synchronization is going to be very important. 00:12:16.000 --> 00:12:21.000 So I would suggest that you use like an NTP server, use a time server, 00:12:21.000 --> 00:12:26.000 and have everybody pointing to the same NTP server, right? 00:12:26.000 --> 00:12:30.000 You might use a public one, like there's pool.ntp.org, 00:12:30.000 --> 00:12:33.000 and that pool is actually a pool of NTP servers, 00:12:33.000 --> 00:12:36.000 so there's not like one server that might fail on you. 00:12:36.000 --> 00:12:39.000 That's usually a pretty safe option for you, okay? 00:12:39.000 --> 00:12:42.000 If for some reason the dependencies fail, 00:12:42.000 --> 00:12:45.000 then you might have to restart your update again. 00:12:45.000 --> 00:12:50.000 And so here you'll see what happens if the FPXD service fails to start 00:12:50.000 --> 00:12:53.000 because of clock synchronization not working, 00:12:53.000 --> 00:12:57.000 you'll start your upgrade over again. 00:12:57.000 --> 00:13:00.000 So here we're going to see how we can make sure our clocks are synchronized, 00:13:00.000 --> 00:13:01.000 right? 00:13:01.000 --> 00:13:02.000 So we're going to find the vCenter server. 00:13:02.000 --> 00:13:04.000 So this is where we're going to do an upgrade. 00:13:04.000 --> 00:13:08.000 We want to make sure that our old vCenter server clock is going to match 00:13:08.000 --> 00:13:10.000 with, you know, what we're deploying to. 00:13:10.000 --> 00:13:12.000 We can log into there as root. 00:13:12.000 --> 00:13:15.000 We can select time, time zones, make sure we're in the correct time zone, 00:13:15.000 --> 00:13:18.000 and we can also make sure if we're going to figure any kind of time 00:13:18.000 --> 00:13:21.000 synchronization, we have NTP enabled, something like that, 00:13:21.000 --> 00:13:28.000 and we can edit that and use whatever time server we want to use. 00:13:28.000 --> 00:13:31.000 So for clock synchronization, we can select how we want to do it. 00:13:31.000 --> 00:13:34.000 We can say none and hope that we get everything, you know, 00:13:34.000 --> 00:13:36.000 in the right time and nothing slides. 00:13:36.000 --> 00:13:38.000 You can synchronize with the host. 00:13:38.000 --> 00:13:41.000 You can have the VMs synchronize with the host they're running on. 00:13:41.000 --> 00:13:45.000 And then if your hosts are using NTP, the VMs should also then be in sync 00:13:45.000 --> 00:13:48.000 because they'll sync with the clock on the host itself. 00:13:48.000 --> 00:13:50.000 That's not a bad option. 00:13:50.000 --> 00:13:52.000 It's not my preferred option. 00:13:52.000 --> 00:13:53.000 I prefer to use NTP. 00:13:53.000 --> 00:13:55.000 I want my host to point to NTP. 00:13:55.000 --> 00:14:00.000 I want my domain controllers pointing to, you know, some kind of NTP. 00:14:00.000 --> 00:14:03.000 I want my vCenter server pointing to an NTP server too. 00:14:04.000 --> 00:14:08.000 And I do like to use an external NTP server personally. 00:14:08.000 --> 00:14:12.000 So what's transferred? 00:14:12.000 --> 00:14:14.000 When we're doing an upgrade, what gets transferred? 00:14:14.000 --> 00:14:17.000 So we have this external database that contains all the vCenter server 00:14:17.000 --> 00:14:18.000 information, right? 00:14:18.000 --> 00:14:21.000 So we're going to dump all this information out of this progress database, 00:14:21.000 --> 00:14:27.000 and it is a relational database, and it's used by vCenter 7, 00:14:27.000 --> 00:14:29.000 and vCenter 8 is going to use the same one. 00:14:30.000 --> 00:14:35.000 And we do this because we don't want to deploy a new vCenter server 00:14:35.000 --> 00:14:39.000 and then have to reconfigure my clusters, my networking. 00:14:39.000 --> 00:14:44.000 If I'm using, you know, distributed virtual, you know, 00:14:44.000 --> 00:14:46.000 switching import groups and things like that, 00:14:46.000 --> 00:14:48.000 I don't want to configure all this over again. 00:14:48.000 --> 00:14:50.000 I want to keep all my logs. 00:14:50.000 --> 00:14:52.000 I want to keep all my log file information. 00:14:52.000 --> 00:14:55.000 I don't want to have to start over again and say, 00:14:55.000 --> 00:14:57.000 I can only look back as far as, you know, 00:14:57.000 --> 00:14:58.000 two weeks ago when I did the upgrade. 00:14:58.000 --> 00:15:00.000 I want all my log information. 00:15:00.000 --> 00:15:02.000 I want all my configuration information. 00:15:02.000 --> 00:15:03.000 I want my matrix. 00:15:03.000 --> 00:15:06.000 I want to make sure that I can go back and look at what was the CPU 00:15:06.000 --> 00:15:11.000 utilization and memory utilization and disk utilization in my environment 00:15:11.000 --> 00:15:14.000 going back, you know, six months ago, eight months ago, a year, 00:15:14.000 --> 00:15:16.000 because I want to be able to see trends. 00:15:16.000 --> 00:15:20.000 And if I have to start over again and then I can only see back two weeks, 00:15:20.000 --> 00:15:23.000 I can only see a two-week trend, which doesn't really tell me much. 00:15:23.000 --> 00:15:25.000 If I can look back over six months, 00:15:25.000 --> 00:15:27.000 I might over six months see a gradual increase. 00:15:27.000 --> 00:15:30.000 But if I look at only two weeks, it might look kind of flat. 00:15:30.000 --> 00:15:32.000 But over a longer period of time, 00:15:32.000 --> 00:15:34.000 I start to see that trend line easing its way up. 00:15:34.000 --> 00:15:37.000 And I can say, okay, based on this, I know I need to look at, you know, 00:15:37.000 --> 00:15:40.000 adding another host to my cluster by the end of the year 00:15:40.000 --> 00:15:44.000 or something like that maybe. 00:15:44.000 --> 00:15:46.000 So why did we do this? 00:15:46.000 --> 00:15:49.000 To keep our configuration consistent, to keep our, you know, 00:15:49.000 --> 00:15:52.000 obviously make it easier to do the upgrade, less overhead, 00:15:52.000 --> 00:15:55.000 and so we can have historical information in our environment. 00:15:55.000 --> 00:15:59.000 That's all super important to do, right? 00:15:59.000 --> 00:16:01.000 So begin the update. 00:16:01.000 --> 00:16:03.000 So we're going to download the ISO from VMware's website. 00:16:03.000 --> 00:16:07.000 Once we've downloaded the ISO, we want to just do an MD5 hash check 00:16:07.000 --> 00:16:10.000 and make sure that nothing has been corrupted during that download. 00:16:10.000 --> 00:16:13.000 Make sure it's all, you know, first of all, 00:16:13.000 --> 00:16:17.000 I got the golden image that VMware stamped and nothing's been changed on that. 00:16:17.000 --> 00:16:19.000 Nothing got, you know, corrupted during the download. 00:16:19.000 --> 00:16:22.000 I've got the bits that VMware wanted me to get, right? 00:16:22.000 --> 00:16:25.000 Then I put that ISO someplace that I can mount. 00:16:25.000 --> 00:16:29.000 I'm going to mount it on the machine that I'm running the upgrade from, right? 00:16:29.000 --> 00:16:31.000 So if I'm going to run it from this Windows server VM, 00:16:31.000 --> 00:16:34.000 I'm going to put it someplace where I can mount it onto that Windows VM 00:16:34.000 --> 00:16:38.000 so I can go into Explorer on that Windows VM 00:16:38.000 --> 00:16:43.000 and I can browse to the setup executable file. 00:16:43.000 --> 00:16:48.000 So when I get ready to do the upgrade, I'm going to configure my hosts, right? 00:16:48.000 --> 00:16:51.000 So on my vCenter server that I want to upgrade, 00:16:51.000 --> 00:16:55.000 I'm going to check my configuration settings, all my general stuff like that. 00:16:55.000 --> 00:16:59.000 I want to make sure that everything is, you know, configured the way I want it. 00:16:59.000 --> 00:17:02.000 SSL settings, verify that vCenter server, right, 00:17:02.000 --> 00:17:06.000 requires verified host SSL certificates. 00:17:06.000 --> 00:17:10.000 So you want to make sure that you're using verified host certificates on this 00:17:10.000 --> 00:17:14.000 deployment, otherwise you're going to have problems when you get into A. 00:17:14.000 --> 00:17:18.000 Because A is going to require that. 00:17:18.000 --> 00:17:21.000 Using the GUI, if we're running off of Windows, for example, 00:17:21.000 --> 00:17:23.000 we're going to find the EXE, right? 00:17:23.000 --> 00:17:28.000 There will be an installer EXE, and we want to execute that. 00:17:28.000 --> 00:17:31.000 Now, what happens is that setup program is going to run, 00:17:31.000 --> 00:17:33.000 and it does it in two phases. 00:17:33.000 --> 00:17:35.000 There will be a phase one and a phase two. 00:17:35.000 --> 00:17:39.000 And it's going to ask me a bunch of questions about deploying the OVA, 00:17:39.000 --> 00:17:41.000 like what host I want to deploy to. 00:17:41.000 --> 00:17:43.000 Am I going to deploy to a vCenter environment? 00:17:43.000 --> 00:17:45.000 Am I going to deploy to an ESXi host? 00:17:45.000 --> 00:17:47.000 It's going to want credentials and things like that, 00:17:47.000 --> 00:17:49.000 and it's going to deploy the OVA. 00:17:49.000 --> 00:17:51.000 So once the OVA is out there and running, 00:17:51.000 --> 00:17:54.000 then the next step kicks in. 00:17:54.000 --> 00:17:56.000 Okay, this completed successfully. 00:17:56.000 --> 00:17:59.000 Step two will be actually the appliance setup. 00:17:59.000 --> 00:18:03.000 And then I'll start getting into the more nitty-gritty of the actual vCenter 00:18:03.000 --> 00:18:04.000 deployment, all right? 00:18:04.000 --> 00:18:07.000 So one step is going to deploy the OVA and give some basic configuration on 00:18:07.000 --> 00:18:08.000 there. 00:18:08.000 --> 00:18:15.000 The next step is going to actually configure vCenter itself. 00:18:15.000 --> 00:18:19.000 So when you start your wizard, the first thing it's going to do is, you know, 00:18:19.000 --> 00:18:21.000 just give you all the options you're going to go through. 00:18:21.000 --> 00:18:22.000 Here's the things you're going to do. 00:18:22.000 --> 00:18:24.000 And it's going to ask you to accept the end-user license agreement. 00:18:24.000 --> 00:18:26.000 So if you actually want to deploy this, 00:18:26.000 --> 00:18:29.000 you're going to need to accept the end-user license agreement, 00:18:29.000 --> 00:18:31.000 and you're going to say next, right? 00:18:31.000 --> 00:18:35.000 This is going to ask you to connect to the source appliance. 00:18:35.000 --> 00:18:38.000 So the source appliance is the machine you're upgrading, right? 00:18:38.000 --> 00:18:40.000 We're going to upgrade this appliance. 00:18:40.000 --> 00:18:42.000 So it's going to ask you for the server name. 00:18:42.000 --> 00:18:44.000 If you're not using the standard default ports, you know, 00:18:44.000 --> 00:18:46.000 what port are you using? 00:18:46.000 --> 00:18:47.000 Your single sign-on credentials. 00:18:47.000 --> 00:18:49.000 So it might be administrator at vSphere.local. 00:18:49.000 --> 00:18:52.000 It might be something else if you configure something else. 00:18:52.000 --> 00:18:57.000 If you're configuring deploying to a host directly, 00:18:57.000 --> 00:19:01.000 then you'll like want root and whatever the root password information is. 00:19:01.000 --> 00:19:05.000 And if you have a non-standard port for that, the port number, right? 00:19:05.000 --> 00:19:08.000 The port credentials for the target machine, 00:19:08.000 --> 00:19:10.000 the vCenter we're going to deploy to. 00:19:10.000 --> 00:19:14.000 The target vCenter information, name and root password, right? 00:19:14.000 --> 00:19:16.000 So root name, root probably, and password. 00:19:16.000 --> 00:19:19.000 Deployment size, what size are we going to do? 00:19:19.000 --> 00:19:21.000 Are we going to do a tiny, a medium, or a large? 00:19:21.000 --> 00:19:23.000 Select your data store. 00:19:23.000 --> 00:19:29.000 You want to pick something that is going to be basically accessible to the 00:19:29.000 --> 00:19:31.000 different machines that are going to need to be running your vCenter 00:19:31.000 --> 00:19:32.000 environment, right? 00:19:32.000 --> 00:19:34.000 So you want to make sure you don't pick, like, a local data store 00:19:34.000 --> 00:19:35.000 or something like that. 00:19:35.000 --> 00:19:37.000 You want to make sure you pick shared storage. 00:19:37.000 --> 00:19:39.000 And then thin provisioning. 00:19:39.000 --> 00:19:42.000 Usually most people are going to want to provision their vCenter server 00:19:42.000 --> 00:19:45.000 with thin provisioning because, by default, when you first deploy, 00:19:45.000 --> 00:19:49.000 it only takes up, you know, 100 gigs, less than 100 gigs. 00:19:49.000 --> 00:19:51.000 If you deploy it in full, it could take up, you know, 00:19:51.000 --> 00:19:55.000 1,000 gigs and things like that, which is a bunch of zeros. 00:19:55.000 --> 00:19:58.000 So usually you deploy that in a thin provisioning. 00:19:58.000 --> 00:19:59.000 And then your network settings. 00:19:59.000 --> 00:20:00.000 IP address. 00:20:00.000 --> 00:20:02.000 Are we using IPv4, IPv6? 00:20:02.000 --> 00:20:03.000 What IP address are we using? 00:20:03.000 --> 00:20:05.000 What subnet mask are we using? 00:20:05.000 --> 00:20:08.000 Default gateway DNS information. 00:20:08.000 --> 00:20:14.000 And, again, make sure whenever DNS servers you configure here that the vCenter 00:20:14.000 --> 00:20:19.000 name and IP address that you entered here are in that DNS server. 00:20:19.000 --> 00:20:23.000 So we can query and we can resolve that vCenter's name 00:20:23.000 --> 00:20:28.000 and IP address from those DNS servers. 00:20:28.000 --> 00:20:30.000 So, again, using the GUI. 00:20:30.000 --> 00:20:32.000 So we've deployed the vCenter server. 00:20:32.000 --> 00:20:35.000 The virtual appliance is deployed, the VM. 00:20:35.000 --> 00:20:37.000 So now we need to configure vCenter, right? 00:20:37.000 --> 00:20:39.000 So now we're going to go through 00:20:39.000 --> 00:20:42.000 and we're going to connect to the source vCenter server, 00:20:42.000 --> 00:20:44.000 where it needs to be coming from, right? 00:20:44.000 --> 00:20:46.000 We're going to select what data we want to upgrade. 00:20:46.000 --> 00:20:48.000 And you probably want to upgrade as much as possible. 00:20:48.000 --> 00:20:50.000 You want to pull as much as you can. 00:20:50.000 --> 00:20:54.000 Do you want to join the customer experience program? 00:20:54.000 --> 00:20:56.000 You can say if you want to join that or not. 00:20:56.000 --> 00:20:59.000 And then you can say, you know, you're complete and all right. 00:20:59.000 --> 00:21:01.000 You want to review these settings and you're going to say okay. 00:21:01.000 --> 00:21:05.000 And once it starts the upgrade, it's going to start pulling over the information. 00:21:05.000 --> 00:21:09.000 It's going to shut down the old vCenter during the process, right? 00:21:09.000 --> 00:21:12.000 And then the new one should be up and running and live. 00:21:12.000 --> 00:21:17.000 And then there will be some upgrade checks that it's going to run to make sure 00:21:17.000 --> 00:21:19.000 that the upgrade process is going to complete successfully. 00:21:19.000 --> 00:21:22.000 So it will attempt to predict if this is going to work 00:21:22.000 --> 00:21:25.000 or not work before it gets too far along. 00:21:25.000 --> 00:21:29.000 It will do some pre-upgrade checks. 00:21:29.000 --> 00:21:32.000 You could do the CLI. 00:21:32.000 --> 00:21:33.000 And why would you do that? 00:21:33.000 --> 00:21:34.000 You have a little bit more control. 00:21:34.000 --> 00:21:36.000 You can script it. 00:21:36.000 --> 00:21:42.000 Really the why for most people is going to be I need to do a lot of vCenters, 00:21:42.000 --> 00:21:47.000 and so I want to create answer files and just do tweets for the, you know, 00:21:47.000 --> 00:21:50.000 individual settings and push that out. 00:21:50.000 --> 00:21:54.000 If I'm only doing one or two, you know, a small number of vCenter servers, 00:21:54.000 --> 00:21:56.000 most people only have one. 00:21:56.000 --> 00:21:57.000 Maybe you have two or three. 00:21:57.000 --> 00:22:02.000 Those are just easier a lot of times just to do it and not worry about 00:22:02.000 --> 00:22:05.000 automating it and things like that and not do it from the CLI. 00:22:05.000 --> 00:22:09.000 You can, when you, you know, part of a couple of the arguments you might do is 00:22:09.000 --> 00:22:13.000 you want to accept the EULA because you don't want to get stuck on that. 00:22:13.000 --> 00:22:15.000 And you can say you want to do a check only. 00:22:15.000 --> 00:22:18.000 That one really might be one of the more common ones is that, okay, 00:22:18.000 --> 00:22:21.000 we're going to plan on deploying this over the weekend, 00:22:21.000 --> 00:22:24.000 but we want to make sure our answer files and things like that are all good. 00:22:24.000 --> 00:22:26.000 So I just do a pre-check only 00:22:26.000 --> 00:22:29.000 and make sure this migration is going to even be successful. 00:22:29.000 --> 00:22:30.000 Right? 00:22:30.000 --> 00:22:32.000 You can do that. 00:22:32.000 --> 00:22:35.000 So post vCenter update. 00:22:35.000 --> 00:22:38.000 So you'll verify the success that it worked. 00:22:38.000 --> 00:22:41.000 Now, if you're going from, like, for example, 6.7, 00:22:41.000 --> 00:22:43.000 we're going to want to go in. 00:22:43.000 --> 00:22:45.000 We're going to log in to the FQDN, right? 00:22:45.000 --> 00:22:46.000 We're going to connect to it. 00:22:46.000 --> 00:22:48.000 Or we can use the IP address and go directly from there, 00:22:48.000 --> 00:22:52.000 but hopefully your FQDN works and we're going to connect that way. 00:22:52.000 --> 00:22:54.000 We're going to shut down. 00:22:54.000 --> 00:22:57.000 If we have an external PSC for authentication, 00:22:57.000 --> 00:22:59.000 we're going to shut that down. 00:22:59.000 --> 00:23:01.000 Then we're going to remove it from the single sign-on domain, 00:23:01.000 --> 00:23:08.000 and we're going to use the internal PCM and not the external one anymore. 00:23:08.000 --> 00:23:12.000 So vSphere 8 only supports, or in the very near future, 00:23:12.000 --> 00:23:15.000 will only support an internal. 00:23:15.000 --> 00:23:18.000 So in 8, it's recommended we just cut off right away. 00:23:18.000 --> 00:23:20.000 We don't want to get to a point to where we still have it, 00:23:20.000 --> 00:23:22.000 and yet we can't log in to our new one. 00:23:22.000 --> 00:23:26.000 So use only the internal PCA. 00:23:26.000 --> 00:23:29.000 And you can see one of your options on your login screen will be to 00:23:29.000 --> 00:23:31.000 download the enhanced authentication plug-in, 00:23:31.000 --> 00:23:35.000 which will allow you to more easily use things like Windows credentials 00:23:35.000 --> 00:23:38.000 or the internal PCA. 00:23:38.000 --> 00:23:40.000 All right? 00:23:40.000 --> 00:23:45.000 So post vCenter server updates, we're going to go through. 00:23:45.000 --> 00:23:47.000 We can say, all right, we've done our vCenter update. 00:23:47.000 --> 00:23:49.000 We're all good, so now what do we want to do? 00:23:49.000 --> 00:23:52.000 We can say we want to configure single sign-on, right? 00:23:52.000 --> 00:23:56.000 So we can say we want to go in and use AD authentication, right? 00:23:56.000 --> 00:23:57.000 We're going to use AD with LDAP, 00:23:57.000 --> 00:23:59.000 or we want to use integrated Windows authentication. 00:23:59.000 --> 00:24:02.000 We've got to make sure we end up at a point to a Windows domain 00:24:02.000 --> 00:24:04.000 controller that's going to join that Windows domain. 00:24:04.000 --> 00:24:09.000 You can also use OpenLDAP 2.4 or later for a single data source for 00:24:09.000 --> 00:24:10.000 authentication. 00:24:10.000 --> 00:24:12.000 Maybe you have an environment where you don't have AD, 00:24:12.000 --> 00:24:14.000 you don't have Windows, you don't run AD. 00:24:14.000 --> 00:24:15.000 There are some of those out there, 00:24:15.000 --> 00:24:18.000 and so you can just use an OpenLDAP database. 00:24:18.000 --> 00:24:22.000 So migration, this is something for Windows. 00:24:22.000 --> 00:24:24.000 We've been talking about doing an upgrade, 00:24:24.000 --> 00:24:27.000 and most of these upgrades we've been discussing so far are going to be 00:24:27.000 --> 00:24:29.000 from virtual clients to virtual clients. 00:24:29.000 --> 00:24:32.000 So what if we have a Windows appliance that's running vCenter, 00:24:32.000 --> 00:24:35.000 and we want to upgrade to the virtual appliance? 00:24:35.000 --> 00:24:38.000 This is not quite as straightforward. 00:24:38.000 --> 00:24:39.000 It is still pretty easy. 00:24:39.000 --> 00:24:41.000 There's tools involved to make it easy, 00:24:41.000 --> 00:24:46.000 but it's not as few steps as it was for going from virtual appliance to 00:24:46.000 --> 00:24:48.000 virtual appliance, okay? 00:24:48.000 --> 00:24:50.000 So if we have a vCenter for Windows, 00:24:50.000 --> 00:24:55.000 we're going to need to convert that to a vCenter virtual appliance, right? 00:24:55.000 --> 00:24:59.000 And then we can go through and upgrade for 7 there, right? 00:24:59.000 --> 00:25:01.000 So we need the migration assistant. 00:25:01.000 --> 00:25:03.000 What's required here is that migration assistant. 00:25:03.000 --> 00:25:08.000 There's going to be a tool that's going to help us get the PSC, 00:25:08.000 --> 00:25:11.000 the vCenter, all over to the virtual appliance. 00:25:11.000 --> 00:25:12.000 If we are running update manager, 00:25:12.000 --> 00:25:14.000 and we have update manager information, 00:25:14.000 --> 00:25:16.000 then we'll also need to run it against our update manager, 00:25:16.000 --> 00:25:19.000 because update manager used to be a separate component, right? 00:25:19.000 --> 00:25:21.000 It wasn't integrated like it is now. 00:25:21.000 --> 00:25:24.000 So we'll also migrate the update manager. 00:25:24.000 --> 00:25:27.000 So now we're going to be on the new vCenter virtual appliance. 00:25:27.000 --> 00:25:30.000 And this new vCenter virtual appliance is going to be one appliance that 00:25:30.000 --> 00:25:35.000 runs both my vCenter information, my authentication information, 00:25:35.000 --> 00:25:38.000 and my update manager all in that one virtual appliance. 00:25:38.000 --> 00:25:41.000 And the migration assistant is going to help you get all those off those 00:25:41.000 --> 00:25:47.000 Windows systems into that one virtual appliance now for the vCenter server. 00:25:47.000 --> 00:25:52.000 So you can see here what we're talking about is we have a vCenter server, 00:25:52.000 --> 00:25:53.000 right, running on Windows, 00:25:53.000 --> 00:25:56.000 and we want to migrate that to a virtual appliance. 00:25:56.000 --> 00:25:58.000 So we're going to run the migration assistant. 00:25:58.000 --> 00:26:01.000 We're going to need to run it against the PSC, 00:26:01.000 --> 00:26:04.000 which is our authentication or single-sign authentication database, 00:26:04.000 --> 00:26:08.000 and we're going to need to run it against the vCenter server itself. 00:26:08.000 --> 00:26:16.000 And both those will get migrated into the virtual appliance, the new VSCA. 00:26:17.000 --> 00:26:20.000 And if we were running update manager, that as well. 00:26:20.000 --> 00:26:21.000 Okay. 00:26:21.000 --> 00:26:23.000 So verified permissions for vCenter server user accounts. 00:26:23.000 --> 00:26:25.000 So if you're going to do a migration, 00:26:25.000 --> 00:26:28.000 here are some of the permissions that your user account is going to have to 00:26:28.000 --> 00:26:29.000 have in order to do that. 00:26:29.000 --> 00:26:31.000 It's going to need to be in the admin group. 00:26:31.000 --> 00:26:35.000 It's going to be able to log on as a service to run these different services 00:26:35.000 --> 00:26:39.000 to migrate these things, can replace the process level token, 00:26:39.000 --> 00:26:41.000 and act as part of the operating system. 00:26:41.000 --> 00:26:42.000 Okay. 00:26:43.000 --> 00:26:48.000 Another key piece of this migration is going to make sure that your PSC 00:26:48.000 --> 00:26:51.000 and your vCenter server certificates are not expired. 00:26:51.000 --> 00:26:52.000 All right. 00:26:52.000 --> 00:26:54.000 Because you'll need to have current certificates for this process to work. 00:26:54.000 --> 00:26:58.000 Of course, as we've mentioned, 00:26:58.000 --> 00:27:01.000 this is going to be a big part of this whole lesson, time synchronization. 00:27:01.000 --> 00:27:05.000 If you're using NTP, make sure that your NTP servers, 00:27:05.000 --> 00:27:07.000 you know, are pointing to the same NTP server. 00:27:07.000 --> 00:27:09.000 Our clocks are in sync. 00:27:09.000 --> 00:27:12.000 We want to have SSL certificate valid. 00:27:12.000 --> 00:27:16.000 And if our clocks are in sync, then our certification won't work. 00:27:16.000 --> 00:27:17.000 Service accounts, 00:27:17.000 --> 00:27:22.000 we need a local service account that has a read permission for both the vCenter 00:27:22.000 --> 00:27:23.000 servers. 00:27:23.000 --> 00:27:25.000 And a system work name. 00:27:25.000 --> 00:27:30.000 Basically, we need to make sure that our systems are named and in DNS. 00:27:30.000 --> 00:27:33.000 With static addresses, we do not want DHCP addresses. 00:27:33.000 --> 00:27:37.000 We want to make sure that our hardware is compliant. 00:27:37.000 --> 00:27:38.000 If our hardware is compliant, 00:27:38.000 --> 00:27:41.000 we have the right amount of hardware deployed and available. 00:27:41.000 --> 00:27:44.000 FQDNs registered in DNS. 00:27:44.000 --> 00:27:46.000 Clock synchronization. 00:27:46.000 --> 00:27:48.000 Again, we keep mentioning the clock synchronization. 00:27:48.000 --> 00:27:52.000 For certificates, for migrating, you know, information back and forth, 00:27:52.000 --> 00:27:54.000 making sure we authenticate properly, 00:27:54.000 --> 00:27:56.000 clock synchronization is super important. 00:27:56.000 --> 00:28:00.000 Make sure your clocks are synchronized. 00:28:00.000 --> 00:28:02.000 Migration system requirements. 00:28:02.000 --> 00:28:03.000 On the target. 00:28:03.000 --> 00:28:05.000 So we've been discussing the source. 00:28:05.000 --> 00:28:08.000 On the target, again, we see admin privileges. 00:28:08.000 --> 00:28:11.000 Now, this one will need more than just read, 00:28:11.000 --> 00:28:13.000 because this is the target we're going to be writing to. 00:28:13.000 --> 00:28:17.000 So we need admin privileges on the other machine so we can get all the 00:28:17.000 --> 00:28:19.000 information dumped into there. 00:28:19.000 --> 00:28:22.000 We need to make sure we have enough storage for this virtual machine. 00:28:22.000 --> 00:28:25.000 If we're bringing over a lot of, like, logs and things like that, 00:28:25.000 --> 00:28:28.000 then we need to have enough room on the virtual disk and our physical 00:28:28.000 --> 00:28:31.000 storage for all those logs to land onto. 00:28:31.000 --> 00:28:34.000 Do we have enough CPU power to make all this happen? 00:28:34.000 --> 00:28:35.000 Can the storage be accessed? 00:28:35.000 --> 00:28:39.000 Obviously having enough storage also means can you access your storage, 00:28:39.000 --> 00:28:40.000 right? 00:28:40.000 --> 00:28:42.000 And then make sure our environment is all set. 00:28:42.000 --> 00:28:45.000 Our hosts are ready, our data stores are ready, 00:28:45.000 --> 00:28:51.000 our virtual appliance is all ready for all this stuff to come over to it. 00:28:51.000 --> 00:28:52.000 Network. 00:28:52.000 --> 00:28:54.000 Again, we keep talking about DNS. 00:28:54.000 --> 00:28:55.000 DNS, super important. 00:28:55.000 --> 00:28:59.000 Static address registered in DNS with the same name as the vCenter 00:28:59.000 --> 00:29:00.000 appliance's name. 00:29:00.000 --> 00:29:03.000 That's going to be really important. 00:29:03.000 --> 00:29:06.000 If you're using DHCP for the virtual appliance, 00:29:06.000 --> 00:29:10.000 you need to make sure that the host and the virtual appliance are on the 00:29:10.000 --> 00:29:12.000 same network. 00:29:12.000 --> 00:29:14.000 But, again, you're going to need to have, like, 00:29:14.000 --> 00:29:18.000 DNS or you want your DHCP server to register the name for you in DNS. 00:29:18.000 --> 00:29:20.000 It's strongly recommended just use static IPs. 00:29:20.000 --> 00:29:22.000 You really don't want to be using DHCP. 00:29:22.000 --> 00:29:26.000 You want to be using static IPs and have static IPs configured on all 00:29:26.000 --> 00:29:29.000 these things for you. 00:29:29.000 --> 00:29:32.000 So some things to be careful for during your migration, okay? 00:29:32.000 --> 00:29:36.000 The source vCenter server you're migrating from is going to shut down, 00:29:36.000 --> 00:29:37.000 right? 00:29:37.000 --> 00:29:38.000 As part of the process, 00:29:38.000 --> 00:29:42.000 we don't want both vCenters online trying to service at the same time. 00:29:42.000 --> 00:29:44.000 We don't want to confuse our hosts and things like that. 00:29:44.000 --> 00:29:48.000 So the source is going to shut down and the new one is going to take over. 00:29:48.000 --> 00:29:54.000 So any solutions that are on that source will become unavailable. 00:29:54.000 --> 00:29:57.000 During that migration, you'll need to add your solutions to the new one. 00:29:57.000 --> 00:29:59.000 Network ID conflicts with the target. 00:30:00.000 --> 00:30:02.000 You don't want IP address conflicts and things like that. 00:30:02.000 --> 00:30:04.000 That can cause a huge problem, right? 00:30:04.000 --> 00:30:08.000 So make sure that we don't have both running at the same time. 00:30:08.000 --> 00:30:10.000 Network adapters, only one adapter is going to be migrated. 00:30:10.000 --> 00:30:13.000 If your vCenter has multiple adapters on there, 00:30:13.000 --> 00:30:15.000 only one adapter setting gets migrated, 00:30:15.000 --> 00:30:20.000 one name gets registered from the DHCP and the IP and things like that. 00:30:20.000 --> 00:30:25.000 Only one adapter setting will get migrated. 00:30:25.000 --> 00:30:27.000 Preparing for this update, 00:30:27.000 --> 00:30:32.000 if you are going from the physical environment, 00:30:32.000 --> 00:30:37.000 Windows VM or physical to the virtual appliance, 00:30:37.000 --> 00:30:41.000 then you're going to need to run that VMware Migration Assistant. 00:30:41.000 --> 00:30:43.000 So you do a lot of the same steps, 00:30:43.000 --> 00:30:45.000 but one of the first things you're going to do is you're going to run the 00:30:45.000 --> 00:30:46.000 VMware Migration Assistant, okay? 00:30:46.000 --> 00:30:50.000 So the Migration Assistant is going to help you go through and it runs your 00:30:50.000 --> 00:30:53.000 prechecks and gives you some reporting information. 00:30:53.000 --> 00:30:58.000 But one of the big things is it's going to migrate that PSC and the virtual 00:30:58.000 --> 00:31:01.000 appliance information to the new virtual appliance, okay? 00:31:01.000 --> 00:31:03.000 So you'll still deploy your virtual appliance, 00:31:03.000 --> 00:31:05.000 but you're going to have your Migration Assistant help you get all the 00:31:05.000 --> 00:31:09.000 information over from the Windows version of vCenter into the virtual 00:31:09.000 --> 00:31:13.000 appliance version of vCenter. 00:31:13.000 --> 00:31:15.000 So if we're going to run the Migration Assistant, 00:31:15.000 --> 00:31:17.000 so you can see here, again, 00:31:17.000 --> 00:31:20.000 we're going to download the installer package for the new vCenter server, 00:31:21.000 --> 00:31:23.000 and we're going to then, you know, 00:31:23.000 --> 00:31:26.000 we're going to mount that onto a machine that we can run it from. 00:31:26.000 --> 00:31:30.000 We're going to go to the folder from our – they say the source machine, 00:31:30.000 --> 00:31:32.000 they mean the source for the ISOs, 00:31:32.000 --> 00:31:35.000 our machine that's going to be running the upgrade wizard, 00:31:35.000 --> 00:31:37.000 the deployment wizard, right? 00:31:37.000 --> 00:31:38.000 And then we're going to go through, 00:31:38.000 --> 00:31:40.000 browse through there to find the executable, 00:31:40.000 --> 00:31:44.000 and then we're going to just run it and say we want to do an upgrade, 00:31:44.000 --> 00:31:45.000 right? 00:31:45.000 --> 00:31:48.000 So when they say the source machine here, 00:31:48.000 --> 00:31:50.000 they're not talking about the source vCenter server. 00:31:50.000 --> 00:31:53.000 They're talking about where we're running the installer from. 00:31:53.000 --> 00:31:55.000 So if we're running from a Windows machine, the installer, 00:31:55.000 --> 00:31:57.000 we mounted the ISO on the Windows box. 00:31:57.000 --> 00:32:02.000 We're going to browse through the ISO to our CD-ROM drive on the Windows VM. 00:32:02.000 --> 00:32:07.000 We're going to find the executable for the migration tool. 00:32:07.000 --> 00:32:10.000 Good idea to run a pre-check just to make sure we're not going to have any 00:32:10.000 --> 00:32:12.000 issues with the upgrade process, right? 00:32:12.000 --> 00:32:15.000 And then we'll go through and we'll run through there, all right? 00:32:15.000 --> 00:32:17.000 So we're going to then, again, 00:32:17.000 --> 00:32:21.000 after you go through the whole migration part of it, the system, 00:32:21.000 --> 00:32:24.000 it will go through, it will deploy the OVA, right? 00:32:24.000 --> 00:32:25.000 We'll select our migration. 00:32:25.000 --> 00:32:28.000 Instead of saying we want to do an update, we want to do a migration. 00:32:28.000 --> 00:32:30.000 And then we follow along the same prompts we would normally. 00:32:30.000 --> 00:32:34.000 And we have a migration tool that's going to help us migrate the PSC, 00:32:34.000 --> 00:32:38.000 the vCenter appliance, and if we have update manager, update manager. 00:32:38.000 --> 00:32:43.000 So some known issues. 00:32:44.000 --> 00:32:47.000 Upgrading vCenter server can cause issues with Lifecycle Manager. 00:32:47.000 --> 00:32:51.000 So if you are running an older version of Lifecycle Manager and then you do 00:32:51.000 --> 00:32:55.000 this upgrading and Lifecycle Manager is not working for you, all you need to do 00:32:55.000 --> 00:32:59.000 is reset the Lifecycle Manager database and let it kind of re-download its 00:32:59.000 --> 00:33:01.000 files and repopulate that. 00:33:01.000 --> 00:33:03.000 So we're going to go to the vCenter shell. 00:33:03.000 --> 00:33:07.000 So we're going to go to the actual virtual appliance shell CLI. 00:33:07.000 --> 00:33:10.000 And we're going to go in and we're going to stop the VMware update manager. 00:33:10.000 --> 00:33:13.000 So you can see service dash control dash dash stop. 00:33:13.000 --> 00:33:14.000 And what do we want to stop? 00:33:14.000 --> 00:33:16.000 The update manager. 00:33:16.000 --> 00:33:19.000 Then we're going to browse through and we're going to reset the database. 00:33:19.000 --> 00:33:22.000 And it tells you there's a command right there for resetting the database. 00:33:22.000 --> 00:33:25.000 Then we're going to remove any patches in the patch store. 00:33:25.000 --> 00:33:27.000 So the R means remove. 00:33:27.000 --> 00:33:28.000 And R is recursive. 00:33:28.000 --> 00:33:31.000 And just want to push through everything that's in that. 00:33:31.000 --> 00:33:33.000 The star means everything in that folder. 00:33:33.000 --> 00:33:35.000 Then once we delete everything in the folder, 00:33:35.000 --> 00:33:38.000 we're going to restart the VMware update manager. 00:33:38.000 --> 00:33:40.000 We'll re-log in, authenticate, 00:33:40.000 --> 00:33:43.000 and it should just download all the new updates and start over again from 00:33:43.000 --> 00:33:44.000 scratch. 00:33:44.000 --> 00:33:49.000 But it'll start over with a new database and the new files with version 8, 00:33:49.000 --> 00:33:51.000 with the new version of vCenter you're running. 00:33:51.000 --> 00:33:54.000 And that should take care of any problems that you have with migrating that 00:33:54.000 --> 00:33:57.000 database over. 00:33:57.000 --> 00:34:01.000 So we discussed the vCSA upgrade process. 00:34:01.000 --> 00:34:04.000 You went over an overview, over your requirements, 00:34:04.000 --> 00:34:07.000 post-configuration steps, and the migration. 00:34:07.000 --> 00:34:08.000 If you have any questions, 00:34:08.000 --> 00:34:11.000 please feel free to reach out to me.