In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","id":41482,"featuredImage":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f38aec9c-1b9f-472b-8bc4-5177f93527b7_thumb.png","label":"Blog","replyCount":0,"views":216,"post":{"id":63100,"author":{"id":7898,"url":"\/members\/aluciani-7898","name":"aluciani","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/77accf89-4f79-48be-81e6-c2ac5507e29b.png","userTitle":"Chevalier","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Chevalier","color":"#660099"},"userLevel":7},"content":"

In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","url":"\/community-blog-154\/nutanix-community-podcast-2022-year-in-review-41482?postid=63100#post63100","creationDate":"2023-01-03T14:40:38+0000","relativeCreationDate":"17 days ago"},"contentType":"article","type":3,"likes":3,"hasCurrentUserLiked":false},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

解决了

ESXI 6.0升级到6.7U2

d
徽章 +4

我正在尝试将ESXI 6.0升级为6.7U2，但是当尝试从Prism IM开始执行此操作时，请在不启用DRS上出现错误。现在我们没有DRS许可证，我们的集群是ESXI 6.0标准许可证，是否有任何方法可以在不需要DRS的情况下进行升级？
我读了几个文档，即使我尝试使用vCenter Update Manager更新，也不会启用DRS。有解决方案吗？

图标

最好的答案ddubuque2019年8月29日，14：01

\n
\nI would always recommend filing a feature request with Nutanix Support for the ability to leverage one-click upgrades with your license type. We have done the same for our 36 ROBO clusters that have licenses that do not include DRS. We have to upgrade 100+ nodes manually and we spend a week plus doing upgrades for hypervisor, firmware, etc... because of this limitation.
\n
\nIf you can sustain the outage, you can shutdown your vms and place all nodes into maintenance mode and kick off the upgrade from VUM of your vcenter is on a different cluster and can still reach the hosts. This would be faster, but would create an outage while the hosts upgrade. You also don't get the peace of mind of only one node going sideways.","className":"post__content__best_answer"}">
查看原件
I'm trying to upgrade ESXi 6.0 to 6.7U2 but when try to do it from Prism im getting errors on DRS not enabled. Now we don't have DRS license, our cluster is ESXi 6.0 Standard License, is there any way to do the upgrade without the needs of DRS ?
I read few documents that even if i try to use vCenter Update manager update will fail becasue DRS is not enabled. Any workaround solution ?<\/p>","quoteUsername":"Dcarbone","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
该主题已关闭以供评论

5个答复

ddubuque
UserLevel 3
徽章 +10
一键升级需要DRS，以便机器可以从主机进行VMOTION，并隔离接收升级的主机。如果您没有DRS功能，则可以使用VUM来升级主机或手动升级，您将无法使用一键式升级。请记住，您需要撤离VM的主机，并关闭该主机上的CVM，然后将主机放置在维护模式下。



我始终建议提交功能请求，并提供Nutanix支持，以便能够使用您的许可证类型利用一键式升级。我们为36个具有不包括DRS的许可的机器人集群做了同样的事情。我们必须手动升级100个以上的节点，我们花了一个星期的时间，以及用于管理程序，固件等的升级，因为这一限制。



如果您可以维持中断，则可以关闭VM，并将所有节点放入维护模式，并从vCenter的VUM启动升级，在不同的集群上，仍然可以到达主机。这会更快，但是在主机升级时会产生中断。您也不会只有一个节点侧向而放心。
大卫·杜比克（David Dubuque）||BKD ||Nutanix NTC 2019和2020 ||Nutanix技术咨询委员会成员||https://darklinkrising.com

\n

\nI would always recommend filing a feature request with Nutanix Support for the ability to leverage one-click upgrades with your license type. We have done the same for our 36 ROBO clusters that have licenses that do not include DRS. We have to upgrade 100+ nodes manually and we spend a week plus doing upgrades for hypervisor, firmware, etc... because of this limitation.

\n

\nIf you can sustain the outage, you can shutdown your vms and place all nodes into maintenance mode and kick off the upgrade from VUM of your vcenter is on a different cluster and can still reach the hosts. This would be faster, but would create an outage while the hosts upgrade. You also don't get the peace of mind of only one node going sideways.","quoteUsername":"ddubuque","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +4

是的，我们在这个集群上运行了vCenter，我们不能同时让所有主机都与戴尔联系，因为我们与他们有硬件，并要求让一些Nutanix的家伙打电话给我们并尝试为了协助我们进行升级...
b ut如果我正确理解，我可以在此过程中使用此过程

  • 将ESXI主机中运行的所有VM转移到集群中的另一个主机
  • 关闭CVM
  • 将主机置于朝鲜模式
  • 使用VUM运行升级

然后为其他主机做同样的事情，对吗？

yeah we have the Vcenter running on this Cluster and we can't have all the host down at the same time, im in contact with dell because we got the hardware with them and asking to get some of the nutanix guys to call us and try to assist us on the upgrade...
b ut if i understand correctely i can do trough VUM one host at the time with this procedure<\/p>
  • transfer all the VM running in that Esxi host to another host in the cluster<\/li>\t
  • Shutdown the CVM<\/li>\t
  • put the host in manteinance mode<\/li>\t
  • run the upgrade with VUM<\/li><\/ul>

    and then doing the same for the other hosts, correct ?<\/p>","quoteUsername":"Dcarbone","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

ddubuque
UserLevel 3
徽章 +10

多数民众赞成在很多。您将需要阅读vum升级程序并正确配置它，但是在高级别上，这是步骤。支持很可能很乐意协助升级。

大卫·杜比克（David Dubuque）||BKD ||Nutanix NTC 2019和2020 ||Nutanix技术咨询委员会成员||https://darklinkrising.com
Thats pretty much it. You'll want to read through VUM upgrade proceedures and get it configured properly, but at a high level that's the steps. Support will likely be more than happy to assist with the upgrade.<\/p>","quoteUsername":"ddubuque","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +4

谢谢 @ddubuque

我将等待首先与Nutanix的支持聊天，如果他们可以提供帮助会更好

Thanks @ddubuque<\/user-mention>\u00a0<\/p>

I\u2019ll wait to chat first with the Nutanix Support, If they can assist will be better \"\ud83d\ude42\"<\/p>","quoteUsername":"Dcarbone","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

s

我知道这是一个月大，但是我可以说我最近如何解决这个问题。LCM 2.3能够在没有DRS的情况下进行。它没有询问它是否已启用。虽然要小心这些升级。我遇到了另一个错误，从6.0升级到6.7U2。VMware将破坏其自己的SSH服务。我们都知道Nutanix和CVM的SSH需要多少，因此它可以使节点停止。

SSH服务从ESXI 6.x升级到6.7 U2后不会响应

I know this is a month old, but I can say how I got around this recently.\u00a0 LCM 2.3 was able to do it without DRS.\u00a0 It didn\u2019t ask if it was enabled or anything.\u00a0 Be careful with these upgrades though.\u00a0 I ran into another bug upgrading from 6.0 to 6.7u2, specifically.\u00a0 VMware will break it\u2019s own SSH service.\u00a0 We all know how much Nutanix and CVM\u2019s need that SSH, so it can bring a node to a halt.<\/p>

SSH service does not respond after upgrading from ESXi 6.x to 6.7 U2<\/a><\/p>","quoteUsername":"Scottie","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu