VC 升级 - xuwang.online

已索引

VCSA 的升级可以在 5480 里通过 update 菜单完成。

也可以通过新版本的 vcsa 的安装程序进行。

这儿以升级到 VC 6.7 为例。

准备

登录VC，打开vc虚拟机的控制台，修改root密码（保持原来的密码即可，否则在升级的过程中会提示密码太久未修改导致升级失败）

挂载ISO 文件，运行H:\vcsa-ui-installer\win32\installer.exe

点击“Upgrade”图标

Connect to source appliance

输入当前VC的IP地址（1.1.1.1)和端口(443)
点击“connect to source”按钮后，输入认证信息：

SSO User name: administrator@xx.com
SSO Password: xxxx
Appliance (OS) root password: xxx

ESXi host or vCenter Server that manages the source appliance
ESXi host or vCenter Server: 1.1.1.2(当前VC所在ESXi主机地址)
HTTPS port: 443
User name: root
Password: xxxx(登录 Host client 的 root 密码)

Appliance deployment target

ESXi host or vCenter Server: 新VC所在ESXi主机，任意选择一台即可
HTTPs port: 443
User name: root
Password: xxx

Set up target appliance VM

VM name: vcsa_6.7_1.1.1.4 （新vc的虚拟机名）
Set root password: xxxx
Confirm root password: xxxx

Select deployment size

选择VC规模（Tiny、Small、Medium、Large、X-Large）
选择规模后，Storage size保持“Default”即可

Select datastore

根据情况选择即可。出于使用体验考虑，建议不要勾选“Enable Thin Disk Mode”。

Configure network settings

配置IP地址、掩码、网关和DNS服务器地址。
注意：目标VC 的IP地址要能够由DNS解析

# nslookup 1.1.1.4
Server:        116.34.9.69
Address:    116.34.9.69#53

1.1.1.4.in-addr.arpa    name = dc01-demo-vc01.example.com.

下一步时，可能会弹出一些告警，根据实际情况进行处理或者忽略。

下面是一个示例：

**Warning**
This ESXi host [1.1.1.2] is managed by vCenter Server [1.1.1.1].
**Resolution**
Make sure the cluster where this ESXi host resides is not set to Fully Automated DRS for the duration of the upgrade process.

**Warning**
vCenter External Extensions
**Description**
This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: Hitachi Storage Services on https://1.11.5:8443/HSS/HNASV2I.zip, vRealize Operations Manager (by VMware) on https://1.1.1.21/vcops-ngc.zip,
**Resolution**
Please ensure extensions are compatible with the new vCenter Server and re-register extensions with the new vCenter Server after upgrade. Please refer to the vSphere documentation on extensions, and the upgrade and interoperability guides.

**Warning**
Files that cannot be used with Update Manager 6.7 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESX 5.5 and lower version host patches baselines.
**Description**
Files that cannot be used with Update Manager 6.7 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESX 5.5 and lower version host patches baselines.
**Resolution**
Please review VMware Update Manager 6.7 Documentation for details

**Warning**
Multiple network adapters(eth0, eth1) detected on the source appliance. During the upgrade only the network information about eth0 will be preserved.
**Resolution**
After upgrade, you can manually add the network adapters that were dropped during the upgrade.

**Warning**
The newly deployed appliance FQDN will be set to 1.1.1.4, although the source appliance FQDN is set to dc01-demo-vc.example.com. This might result in inability to access the appliance through FQDN dc01-demo-vc.example.com
**Description**
The newly deployed appliance FQDN will be set to 1.1.1.4, although the source appliance FQDN is set to dc01-demo-vc.example.com. This might result in inability to access the appliance through FQDN dc01-demo-vc.example.com
**Resolution**
To preserve current appliance FQDN, verify that the FQDN matches the configuration of the vCenter Single Sign-On and the vCenter Server certificates. To verify that the FQDN is DNS resolvable - execute `dig dc01-demo-vc.example.com +short` locally on the appliance, or `nslookup dc01-demo-vc.example.com` on a windows machine

Select upgrade data

Select the data that you want to copy from the source vCenter Server.

Configuration (3.06 GB) Estimated downtime: 39 minutes
Configuration and historical data (events and tasks) (3.18G)
Configuration and historical data (events, tasks and performance metrics) (3.29 GB)

下一步时，可能会弹出一些告警，根据实际情况进行处理或者忽略。

**Information**
If using Auto Deploy, update the DHCP settings and update the TFTP settings with the new set of tramp files from the new Auto Deploy server.

**Information**
vSphere 6.7 disables the TLS 1.0 and TLS 1.1 protocols for improved security. Note: Some applications might support only the older protocols. To revert to the less secure TLS 1.0 and TLS 1.1 protocols, run the TLS Reconfigurator tool. Tool location: vCenter Server Appliance: /usr/lib/vmware-TlsReconfigurator/VcTlsReconfigurator vCenter Server on Windows: %VMWARE_CIS_HOME%\TlsReconfigurator\VcTlsReconfigurator See https://kb.vmware.com/kb/2147469 for details.

VC 升级

admin • 2022 年 10 月 26 日

已索引

VCSA 的升级可以在 5480 里通过 update 菜单完成。

也可以通过新版本的 vcsa 的安装程序进行。

这儿以升级到 VC 6.7 为例。

准备

登录VC，打开vc虚拟机的控制台，修改root密码（保持原来的密码即可，否则在升级的过程中会提示密码太久未修改导致升级失败）

挂载ISO 文件，运行H:\vcsa-ui-installer\win32\installer.exe

点击“Upgrade”图标

Connect to source appliance

输入当前VC的IP地址（1.1.1.1)和端口(443)
点击“connect to source”按钮后，输入认证信息：

SSO User name: administrator@xx.com
SSO Password: xxxx
Appliance (OS) root password: xxx

Appliance deployment target

ESXi host or vCenter Server: 新VC所在ESXi主机，任意选择一台即可
HTTPs port: 443
User name: root
Password: xxx

Set up target appliance VM

VM name: vcsa_6.7_1.1.1.4 （新vc的虚拟机名）
Set root password: xxxx
Confirm root password: xxxx

Select deployment size

选择VC规模（Tiny、Small、Medium、Large、X-Large）
选择规模后，Storage size保持“Default”即可

Select datastore

根据情况选择即可。出于使用体验考虑，建议不要勾选“Enable Thin Disk Mode”。

Configure network settings

配置IP地址、掩码、网关和DNS服务器地址。
注意：目标VC 的IP地址要能够由DNS解析

# nslookup 1.1.1.4
Server:        116.34.9.69
Address:    116.34.9.69#53

1.1.1.4.in-addr.arpa    name = dc01-demo-vc01.example.com.

下一步时，可能会弹出一些告警，根据实际情况进行处理或者忽略。

下面是一个示例：

**Warning**
This ESXi host [1.1.1.2] is managed by vCenter Server [1.1.1.1].
**Resolution**
Make sure the cluster where this ESXi host resides is not set to Fully Automated DRS for the duration of the upgrade process.

**Warning**
vCenter External Extensions
**Description**
This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: Hitachi Storage Services on https://1.11.5:8443/HSS/HNASV2I.zip, vRealize Operations Manager (by VMware) on https://1.1.1.21/vcops-ngc.zip,
**Resolution**
Please ensure extensions are compatible with the new vCenter Server and re-register extensions with the new vCenter Server after upgrade. Please refer to the vSphere documentation on extensions, and the upgrade and interoperability guides.

**Warning**
Files that cannot be used with Update Manager 6.7 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESX 5.5 and lower version host patches baselines.
**Description**
Files that cannot be used with Update Manager 6.7 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESX 5.5 and lower version host patches baselines.
**Resolution**
Please review VMware Update Manager 6.7 Documentation for details

**Warning**
Multiple network adapters(eth0, eth1) detected on the source appliance. During the upgrade only the network information about eth0 will be preserved.
**Resolution**
After upgrade, you can manually add the network adapters that were dropped during the upgrade.

**Warning**
The newly deployed appliance FQDN will be set to 1.1.1.4, although the source appliance FQDN is set to dc01-demo-vc.example.com. This might result in inability to access the appliance through FQDN dc01-demo-vc.example.com
**Description**
The newly deployed appliance FQDN will be set to 1.1.1.4, although the source appliance FQDN is set to dc01-demo-vc.example.com. This might result in inability to access the appliance through FQDN dc01-demo-vc.example.com
**Resolution**
To preserve current appliance FQDN, verify that the FQDN matches the configuration of the vCenter Single Sign-On and the vCenter Server certificates. To verify that the FQDN is DNS resolvable - execute `dig dc01-demo-vc.example.com +short` locally on the appliance, or `nslookup dc01-demo-vc.example.com` on a windows machine

Select upgrade data

Select the data that you want to copy from the source vCenter Server.

Configuration (3.06 GB) Estimated downtime: 39 minutes
Configuration and historical data (events and tasks) (3.18G)
Configuration and historical data (events, tasks and performance metrics) (3.29 GB)

下一步时，可能会弹出一些告警，根据实际情况进行处理或者忽略。

**Information**
If using Auto Deploy, update the DHCP settings and update the TFTP settings with the new set of tramp files from the new Auto Deploy server.

**Information**
vSphere 6.7 disables the TLS 1.0 and TLS 1.1 protocols for improved security. Note: Some applications might support only the older protocols. To revert to the less secure TLS 1.0 and TLS 1.1 protocols, run the TLS Reconfigurator tool. Tool location: vCenter Server Appliance: /usr/lib/vmware-TlsReconfigurator/VcTlsReconfigurator vCenter Server on Windows: %VMWARE_CIS_HOME%\TlsReconfigurator\VcTlsReconfigurator See https://kb.vmware.com/kb/2147469 for details.