• 欢迎访问LLYCLOUD information technical share center (ITSC),Linux 安全,Linux 系统,推荐使用最新版火狐浏览器和Chrome浏览器访问本网站,欢迎加入LLYCLOUD QQ群
  • 如果您觉得本站非常有看点,那么赶紧使用Ctrl+D 收藏LLYCLOUD ITSC吧

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

vmware Akide_Liu 9个月前 (04-23) 1000次浏览 0个评论
文章目录[隐藏]

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

vCenter Server Appliance 6.5u2 升级 6.7u2教程

如果vSphere环境运行的是6.0或更高版本,则可以使用vSphere 6.7中提供的迁移工具轻松地将vCenter Server迁移到版本6.7。

全新的vCSA安装相比,升级是用于复杂环境或在原始vCenter Server中配置了耗时设置的首选方法。 目前,vCSA 6.0或6.5 U1支持直接vCSA升级到版本6.7,但已经宣布即将推出的vCSA 6.7 U1更新版本也将支持从6.5 U2版本升级。

虽然升级过程不会删除原始vCSA,但在继续升级之前,请确保有可用的备份可用于在出现问题时还原原始vCSA。

Troubleshooting list

1.vCenter Server or Platform Services Controller certificate validation error messages for external solutions in environments with a External Platform Services Controller (stage1)
在具有外部 Platform Services Controller 的环境中外部解决方案出现 vCenter Server 或 Platform Services Controller 证书验证错误消息

Aura

2121701, Some solutions, such as VMware vCenter Site Recovery Manager, VMware vSphere Replication, or VMware vCenter Support Assistant are always installed on a different machine than the associated vCenter Server system or Platform Services Controller that manages the certificates for the solution.  If you replace the Machine SSL certificate of a vCenter Server system or a Platform Services Controller in an environment with an External Platform Services Controller, a connection error results when the solution attempts to connect to the vCenter Server. The reason is that the vCenter Server and the Platform Services Controller use the new certificate, but the corresponding service registrations with the VMware Lookup Service are not updated. When solutions connect to vCenter Server or Platform Services Controller, they look at the service registration, which includes the service URL and the sslTrust string. By default, the sslTrust string is the Base 64 encoded old certifica

2.6.5u2f to 6.7u2 Pre-upgrade Check Failed. 6.5u2f to 6.7u2 预检查失败(stage2)

3.An error occurred while performing security operation: Failed to add user: cm to group: cis' could not configure the Component Manager security setting. 因为安全原因无法添加用户导致了无法继续执行复制操作(stage 2)

目录

1.全新安装vCSA 6.7
2.升级安装vCSA 6.5 到 6.7
3.升级安装ESXi 6.5 到 6.7
4.升级安装vSAN 6.6 到 6.7

先决条件

在继续升级之前,必须禁用源vCSA中的vSphere DRS功能或将其设置为手动,以避免在升级过程中出现vCSA问题。

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

升级vCSA

升级到6.7版是一个两阶段的过程:

  • 第1阶段 - 部署新设备
  • 第2阶段 - vCSA的配置

第1阶段 - 部署设备

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

第2阶段 - vCSA的配置

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

您可能会收到有关以下内容的警告:

  • 源vCenter Server所在的群集必须将vSphere DRS功能未设置为“全自动”
  • 不会复制与Update Manager 6.7 不兼容的基准
  • 有关无法迁移的vCenter Server扩展的警告
  • 如果源设备配置了多个NIC,则仅保留Eth0相关的网络信息

修复可能阻止升级的检测到的问题(在更糟糕的情况下,您需要重新部署vCSA)。 单击“ 关闭”继续。

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集
这里我们可以在vmware community找到答案。
这个问题的因为我从6.5u2f升级到6.7u1(当时使用的是6.7u1的镜像)。产生了一个叫做back-in-time的问题(翻译过来叫时光倒流的问题)。我们不可以使用比6.7发布更新的6.5版本来升级这样会导致错误。发布时间版本库:VMware knowledge base
简单来说必须使用比你现在6.5发布日期更的的6.7版本!
Command> software-packages install --url --acceptEulas

[2019-04-19T09:39:35.109] : Evaluating packages to stage...

[2019-04-19T09:39:35.109] : Verifying staging area

[2019-04-19T09:39:36.109] : Validating software update payload

[2019-04-19T09:39:36.109] : Validation successful

[2019-04-19 09:39:36,436] : Copying software packages 134/134

[2019-04-19 09:59:51,214] : Running test transaction ....

[2019-04-19 09:59:53,289] : Running pre-install script.....

[2019-04-19 09:59:58,329] : Upgrading software packages ....

[2019-04-19T10:04:18.109] : Setting appliance version to 6.7.0.30000 build 13010631

[2019-04-19 10:04:18,220] : Running pre-patch script.....

[2019-04-19 10:04:19,225] : Running post-patch script.....

[2019-04-19T10:05:32.109] : Packages upgraded successfully, Reboot is required to complete the installation.

然后重启:

shutdown reboot -r "patch reboot"
Reference:
VMware Portal Maintenance

I'm attempting to upgrade vCSA from 6.5U2c to 6.7U1, but keep getting a pre-ugprade check failed message. Error Message: Cannot validate target

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

 

Aura

55863, To learn more about firstboot issues see: Understanding and Troubleshooting vCenter Server and vCenter Server Appliance 6.7 Firstboot Install/Deployment, Upgrade, or Migration Failures​.To collect a log bundle or review log files for a vCenter Server Appliance install, upgrade, or migration issues reference Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure.  The relevant logs will be on the newly deployed appliance.  firstbootStatus.json contains the following:  "failedSteps": "cmfirstboot"  cmfirstboot.py_####_stderr.log contains the following:   PAM: Authentication token is no longer valid An error occurred while performing security operation: 'Failed to add user: cm to group: cis'  Note: vCenter Server Appliance - Firstboot logs are located in the /var/log/firstboot directory.

Aura

2148354, Installing, migrating or upgrading PSC Appliance 6.5 onto a newly created ESXi Server may fail with the following error in stage 2 section during PSC setup:Note: Refer the attached images in this article to view the UI examples of these error messages. You see this error if the setup fails during Component Manager's security configuration: An error occurred while performing security operation: 'Failed to add user: cm to group: cis' Could not configure the Component Manager security settings. Error 'Services might not be working as expected'ORA problem occurred while - Starting VMware Component Manager In the / var/log/messages of the Appliance, if you find these two messages showing the time change and the root password being expired, the clock running on the ESXi Server hosting the appliance VM is incorrect.localhost systemd[1]: systemd 228 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集

 


Llycloud ITSC , 版权所有丨如未注明 , 均为原创丨本网站采用BY-NC-SA协议进行授权
转载请注明原文链接:Part 2 vCenter 6.5 升级 6.7,vCenter升级采坑合集
喜欢 (0)
[]
分享 (0)
发表我的评论
取消评论

表情 贴图 加粗 删除线 居中 斜体 签到

Hi,您需要填写昵称和邮箱!

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址