你的升级指南

  • 2021年7月30日
  • 0回答
  • 180的浏览量
H
排名
徽章 ＋３

我们的大多数客户每隔几个月升级一次他们的基础设施，本指南帮助我们的客户了解如何升级以及从这个过程中可以期待什么。

在旧版本的AOS中，升级是通过“一键式”或“升级软件”来完成的。使用新版本中可用的LCM，升级更加简单和直接。以下是理解LCM的先决条件和LCM如何工作的文档:

https://portal.nutanix.com/page/documents/details?targetId=Life-Cycle-Manager-Guide-v20:Life-Cycle-Manager-Guide-v20

LCM每次只在一个节点上工作，如果计划的节点成功升级到目标版本，则升级将继续到下一个节点。可以通过Prism UI中的“LCM”监控LCM升级任务。

在升级期间，用户虚拟机基本上不需要停机。考虑到性能问题，最好总是为升级安排维护窗口，特别是对于使用1G NIC卡的集群。请参阅以下文档，以了解升级组件的顺序:

https://portal.nutanix.com/page/documents/details?targetId=Acropolis-Upgrade-Guide-v5_19%3Aupg-upgrade-recommended-order-t.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070

了解组件是否可以从当前版本升级到目标版本是非常重要的，这里是检查相同的URL:

https://portal.nutanix.com/#/page/upgradePaths

下面是检查AOS和hypervisor之间兼容性的指南:

https://portal.nutanix.com/#/page/compatibilitymatrix

如果你的硬件没有在上面的矩阵中列出，请检查供应商的网站，了解它们与超融合和hypervisor的兼容性。例如，要检查DELL硬件与AOS和管理程序的兼容性，

dell.com——>支持——>浏览所有产品——>融合基础设施——>超融合——>XC系列电器——>选择XC服务器——>浏览文档——>在搜索栏中输入“兼容性矩阵”。

对于所有其他组件，如hypervisor，固件，基础等等;检查要升级的可用版本的方法是执行LCM库存。执行LCM库存将获取每个组件的所有兼容版本。“执行LCM库存”是一个无干扰的过程，也可以自动化。LCM到达download.nutanix.com以获取安装程序。请注意，其他供应商的管理程序必须手动上传。

下面是一个有助于理解卫城升级的链接:

https://portal.nutanix.com/page/documents/details?targetId=Acropolis-Upgrade-Guide-v5_18:upg-acropolis-upgrade-welcome-c.html

NCC升级:

要升级的Nutanix基础设施的第一个和最重要的组成部分是NCC。这是因为NCC确保在升级期间没有误报，并在升级的任何时刻提供集群运行状况检查的准确报告。这是一个完全无干扰的升级，是独立于所有其他组件。

升级市场:

请参考以下文档了解AOS升级的前提条件:

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v510%3Aupg-cluster-aos-upgrade-prerequisites-pe-c.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070

每个节点升级AOS的平均时间为15分钟。拥有两个节点的集群比拥有三个或更多节点的集群花费的时间更长。升级前测试是在升级前进行的，用于检查集群是否准备好升级AOS。本文中列出了预检查以及升级前测试失败的潜在原因和解决方案:portal.nutanix.com/kb/6524

在成功完成升级前测试后，获取的AOS软件被上传至本地的每个CVM，每次一个，并在每次CVM升级结束时观察到重启。当一个CVM关闭时，流量会被路由到集群中的另一个CVM。

升级棱镜中心:

要了解电脑升级的工作原理，请参阅:

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-Prism-v510%3Amul-upgrade-wc-t.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070

升级一台独立PC的平均时间是25分钟，扩展PC的平均时间是1小时。升级前需要进行升级前测试。所有的测试都必须通过才能进行升级。在升级前测试期间没有停机时间。请参阅以下文档，以了解每个升级前测试和失败测试的潜在原因:portal.nutanix.com/kb/6524

固件升级:

运行升级前测试来验证集群是否准备好进行hypervisor升级。除了某些DELL模块外，LCM应该能够升级所有的固件。“全部更新”选项让LCM智能地工作，并按顺序执行固件升级。客户无需首先担心BMC或BIOS升级，因为LCM会处理这些问题。防火墙的要求在文档中列出:

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v510%3Awc-support-firewall-wc-c.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070

LCM每次升级一个节点的固件，并确保在继续下一个节点之前服务已启动，DR正常。在固件升级期间，节点多次引导到phoenix，这是正常的，不用担心。

升级管理程序:

确保在Hypervisor升级之前升级NCC和固件。

关于AHV:请参阅此处的文档https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v510%3Aupg-hypervisor-upgrade-ahv-c.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070

对于ESXi:请参考此处的文档

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v510:upg-hypervisor-upgrade-esxi-c.html

Hyper V:请参考此处的文档

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v510:upg-hypervisor-upgrade-hyperv-c.html

虚拟化环境支持策略请参见portal.nutanix.com/kb/3123

升级前的测试是在升级之前运行的，请参考以下相同的KB: portal.nutanix.com/kb/6524

LCM管理程序升级更吸引人的地方是，它自动迁移虚拟机，将主机和CVM置于维护模式，执行升级并使主机联机。LCM将确保数据弹性是OK的，然后再继续到下一个主机。


下面是下载Nutanix软件的网址:

https://portal.nutanix.com/page/downloads/list?a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070


问题升级?查看portal.nutanix.com以获取来自LCM失败任务的常见错误签名。

\u00a0<\/p>

Most of our customers upgrade their infrastructure once every couple of months and this guide helps our customers understand\u00a0\u00a0how to upgrade and what to expect from the process.\u00a0<\/span><\/p>

In older versions of AOS, upgrades were done using \u201cone click\u201d or \u201cupgrade software\u201d. With LCM available in newer versions, the upgrades are much simpler and straightforward. Here\u2019s the documentation\u00a0 to understand pre-requisites of LCM and how LCM works:<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Life-Cycle-Manager-Guide-v20:Life-Cycle-Manager-Guide-v20<\/span><\/p>

\u00a0<\/p>

The LCM works on one-node at a time and if the upgrade proceeds to the next node if the scheduled node is successful in upgrading to the target version. The LCM upgrade tasks can be monitored from \u201cLCM\u201d in Prism UI.<\/span><\/p>

\u00a0<\/p>

There is essentially no downtime required for the user VMs during the upgrades.\u00a0 With regards to concerns about performance, it\u2019s always best to schedule maintenance window for the upgrades, especially with the cluster with 1G NIC cards. Please take a look at the following documentation to understand the sequence of components to be upgraded:<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Acropolis-Upgrade-Guide-v5_19%3Aupg-upgrade-recommended-order-t.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070<\/span><\/p>

\u00a0<\/p>

It is quite important to understand if the components can be upgraded to target version from the present version and here\u2019s the URL to check the same:<\/span><\/p>

https:\/\/portal.nutanix.com\/#\/page\/upgradePaths<\/span><\/p>

\u00a0<\/p>

Here\u2019s the guide to check compatibility between the AOS and hypervisor:<\/span><\/p>

https:\/\/portal.nutanix.com\/#\/page\/compatibilitymatrix<\/span><\/p>

\u00a0<\/p>

If your hardware isn\u2019t listed in the above matrix please check the vendor website for their compatibility with hyperconvergence and hypervisor. For example, to check the DELL hardware compatibility with AOS and hypervisors,\u00a0<\/span><\/p>

\u00a0<\/p>

dell.com-->support-->browse all products-->converged infrastructure--->hyperconverged--->XC series appliances-->choose XC server-->browse documentation--->type \"compatibility matrix\" in search bar.<\/span><\/p>

\u00a0<\/p>

For all the other components like hypervisor, firmware, foundation etc; the to-go way of checking the available versions to upgrade would be to perform the LCM inventory. Performing LCM inventory will fetch all the compatible versions for each component. \u201cPerforming LCM inventory\u201d is a non-disruptive process and can be automated as well. The LCM reaches download.nutanix.com to fetch the installers. Please note that hypervisors for other vendors have to be manually uploaded.\u00a0<\/span><\/p>

\u00a0<\/p>

Here\u2019s a helpful link to understand Acropolis upgrades:<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Acropolis-Upgrade-Guide-v5_18:upg-acropolis-upgrade-welcome-c.html<\/span><\/p>

Upgrading NCC:<\/span><\/p>

First and foremost component of the Nutanix infrastructure to be upgraded is the NCC. This is because NCC makes sure that there are no false positives during the upgrades and gives accurate reports of the cluster health check at any point in the upgrade. This is a completely non-disruptive upgrade and is independent of all other components.<\/span><\/p>

\u00a0<\/p>

Upgrading AOS:\u00a0<\/span><\/p>

Please refer to the following documentation to understand pre-requisites of AOS upgrade:<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Web-Console-Guide-Prism-v510%3Aupg-cluster-aos-upgrade-prerequisites-pe-c.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070<\/span><\/p>

\u00a0<\/p>

The average time taken to upgrade AOS on each node is 15 minutes. The clusters with two nodes take longer than clusters with three or more nodes.The pre-upgrade tests are conducted before the upgrade to check if the cluster is ready for AOS upgrade. Pre-checks along with the potential causes for pre-upgrade test failures and solutions are listed in the article here: portal.nutanix.com\/kb\/6524<\/span><\/p>

\u00a0<\/p>

After successful completion of pre-upgrade tests, the fetched AOS software is uploaded locally to each of the CVMs, one at a time and reboot is observed\u00a0 at the end of each CVM upgrade. During the time when a CVM is down, the traffic is routed to another CVM in the cluster.<\/span><\/p>

\u00a0<\/p>

Upgrading Prism Central:<\/span><\/p>

\u00a0<\/p>

To understand how the PC upgrades work, please refer to:<\/span><\/p>

\u200b\u200bhttps:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Prism-Central-Guide-Prism-v510%3Amul-upgrade-wc-t.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070<\/span><\/p>

\u00a0<\/p>

The average time to upgrade a standalone PC is 25 minutes and scale out PC is 1 hour. Pre-Upgrade tests are conducted before starting the PC upgrade. All the tests have to be passed to proceed to the upgrade. There is no downtime during the pre-upgrade tests. Please refer to the below documentation to understand each of the pre-upgrade tests and potential causes of the failed tests: portal.nutanix.com\/kb\/6524<\/span><\/p>

\u00a0<\/p>

Upgrading\u00a0 firmware:<\/span><\/p>

The pre-upgrade tests are run to verify if the cluster is ready for hypervisor\u00a0 upgrade. Apart from certain DELL modules, LCM should be able to upgrade all firmware. The \u201cupdate all\u201d option lets the LCM work intelligently and perform firmware upgrades in sequence. Customers need not worry about BMC or BIOS upgrading first as LCM takes care of it. The firewall requirements are listed in the documentation here:<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Web-Console-Guide-Prism-v510%3Awc-support-firewall-wc-c.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070<\/span><\/p>

\u00a0<\/p>

LCM upgrades firmware one node at\u00a0 a time and makes sure the services are up and DR is OK\u00a0 before proceeding to the next node. The node boots into phoenix multiple times while the firmware upgrade is running and this is normal and not to worry.\u00a0<\/span><\/p>

\u00a0<\/p>

Upgrading the Hypervisor:<\/span><\/p>

Make sure to upgrade NCC and Firmware prior to Hypervisor upgrade.<\/span><\/p>

\u00a0<\/p>

For AHV: Please refer to the documentation here https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Web-Console-Guide-Prism-v510%3Aupg-hypervisor-upgrade-ahv-c.html&a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070<\/span><\/p>

\u00a0<\/p>

For ESXi: Please refer to the documentation here<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Web-Console-Guide-Prism-v510:upg-hypervisor-upgrade-esxi-c.html<\/span><\/p>

\u00a0<\/p>

For Hyper V: Please refer to the documentation here<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Web-Console-Guide-Prism-v510:upg-hypervisor-upgrade-hyperv-c.html<\/span><\/p>

\u00a0<\/p>

For the hypervisor support policy, please refer to portal.nutanix.com\/kb\/3123<\/span><\/p>

Pre-upgrade tests are run before the upgrades, please refer to the following KB about the same:\u00a0 portal.nutanix.com\/kb\/6524\u00a0<\/span><\/p>

\u00a0<\/p>

What\u2019s more appealing about LCM hypervisor upgrades is that it automates the migration of VMs, putting the host and CVM in Maintenance mode, performing the upgrade\u00a0 and bringing back the host online. The LCM will make sure Data\u00a0 Resiliency is OK before proceeding to the next host.\u00a0<\/span><\/p>


\u00a0<\/p>

Here\u2019s the URL to download the Nutanix software:<\/span><\/p>

https:\/\/portal.nutanix.com\/page\/downloads\/list?a=6c512d227c25fcff1f8bac1b65e44554c4ca6cf8a558507fc607fc027662213f282f2f85696a4070<\/span><\/p>


Issues with Upgrade? Check the portal.nutanix.com for the common error signatures from LCM failure tasks.\u00a0<\/p>","quoteUsername":"Haritha Andal","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

本主题已关闭供评论
Baidu