ESXI 5.5U2

t
UserLevel 2
徽章 +14
你好，

是否有官方立场升级到/使用ESXI 5.5U2作为安装媒体？我看到在受支持的管理程序列表上明确指定了U1，是否有U2认证的目标日期？
    \n
    \nIs there an official stance on upgrading to\/using ESXi 5.5U2 as install media? I see that U1 is specified explicitly on the supported Hypervisor list, is there a target date for U2 certification?","quoteUsername":"tjagoda","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    6个答复

    F
    徽章 +4
    我刚刚升级了NX1350到VMware ESXI 5.5补丁ESXI550-UPDATE02 Build-2068190使用命令行选项，没有问题，但必须在上一个主题中提到Nutanix Engineers Dlink7＆Paulr：FDM和Pynfs of the uninstall/re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-安装pynfs。
    dlink7
    UserLevel 4
    徽章 +19
    用语中的主要补丁是60-90天

    未成年人前进。
    \n
    \nMinor go right ahead.","quoteUsername":"dlink7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    k
    徽章 +1
    嗨，dlink7，

    现在发布有关ESXI 5.5U2的任何文件？由于购买了客户的NX-3360 64GB DOM，这是否意味着它没有FDM和PYNFS问题？

    此外，如果我升级到ESXI5.5U2，并且可以忽略10GB驱动程序，那么所有Nutanix节点现在都在ESX 5.5.0版本中。

    问候，
    开尔文
    \n
    \nAny document is released now about ESXi 5.5U2? Since customer is purchased NX-3360 64GB DOM, is that mean it do not have fdm and pynfs issue(s)?
    \n
    \nAdditionally, all of the nutanix node now is in ESX 5.5.0 version, if I upgrade to ESXi5.5U2 and the 10Gb driver can be ignored, right?
    \n
    \nRegards,
    \nKelvin","quoteUsername":"kelvinwong927","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    乔恩
    秩
    UserLevel 6
    徽章 +29
    开尔文，
    我们现在正式支持5.5 U2。

    如果您有64GB的DOM，那么您是正确的，这些问题已经消失。

    RE 10GB驱动程序：我不确定您的意思是什么，但是如果您升级到5.5 U2，请确保您升级到NCC 1.3（或当前GA版本），并运行“ NCC Health_checks Run_all”，以验证您的已安装驱动程序和确保您处于正确的水平。
    乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
    \nWe support 5.5 U2 now officially.
    \n
    \nIf you have 64GB DOM's, you are correct, those issues are gone.
    \n
    \nRE 10Gb driver: I am not sure what you mean specifically, but if you upgrade to 5.5 U2, make sure you upgrade to NCC 1.3 ( or current GA version), and run \"ncc health_checks run_all\", that will validate your installed drivers and make sure you are at the right level.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Donniebrasco
    秩
    UserLevel 4
    徽章 +18
    乔恩便笺的小更新。

    ESX 5.5 U2A在VMware网站上可用供下载。由于某种原因，VMware已从其网站上删除了ESX 5.5 U2图像。
    \n
    \nESX 5.5 U2a is availble on VMware website for download. For some reason VMware has removed ESX 5.5 U2 image from their website.","quoteUsername":"DonnieBrasco","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    s
    徽章 +4
    嗨，乔恩，

    我遇到了VDS从标准开关迁移的问题，尤其是使用VMK（管理）接口。我正在使用相同的ESXI5.5U2（2068190）版本。当我乘坐主机的直接控制台时，主人失去了连接，发现了以下内容：

    VMHOST001失败：无法获得模块CBRC_FILTER启用状态。（错误与配置文件交互file/etc/vmware/esx.conf：在等待锁定时的时机。握住锁的是托管工人（34271）。这可能是临时条件。请再次尝试您的操作。）

    然后，我输入了根和密码以登录控制台。然后运行以下命令以带回连接：

    ESXCFG -VMKNIC -L
    发现“管理网络”“启用”设置为false（从技术上讲，它被禁用）

    它不允许启用，我再次运行了命令ps -t |grep“ dcui”找到DCUI的过程ID，然后

    #kill 35112

    ESXCFG -VMKNIC -E“管理网络”，然后主机开始连接ping和vCenter。

    知道为什么会发生这种情况以及任何修复或补丁吗？
    \n
    \nI had the problem with vDS migration from Standard switch especially with VMK (management) interface. I am using the same ESXi5.5U2 (2068190) version. The host lost the connection, when I took direct console of the host, found the below:
    \n
    \nvmhost001 Failed: Failed to get enabled state for module cbrc_filter. (Error interacting with configuration file \/etc\/vmware\/esx.conf: Timedout while waiting for lock. \/etc\/vmware\/esx.conf.LOCK. to be released. Another Process has kept this file locked for 20 seconds. The process currently holding the lock is hosted-worker(34271). This is likely temporary condition. Please try your operation again.)<\/i><\/b>
    \n
    \nThen, I entered root and password to login the console. Then ran the following commands to bring back the connection:
    \n
    \nesxcfg-vmknic -l
    \nFound that \"Managment Network\" \"Enabled\" set to false (technically it was disabled)
    \n
    \nit is not allowing to enable, again, I ran the command ps -t | grep \"dcui\" to find the process id for dcui, then
    \n
    \n#kill 35112
    \n
    \nesxcfg-vmknic -e \"Management Network\" , then host started to ping and vcenter connected.
    \n
    \nAny idea why this happening and any fix or patch?","quoteUsername":"shan","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