Nutanix文件集群配置从UI更改

2年前
2019年4月28日
1回复
1970年的观点

UserLevel 2

Proyoung
Nutanix员工
11个答复

现在可以从Prism UI接口更新Nutanix文件群集名称，文件服务器VM配置和网络配置。让我们一一了解这些选项。

1. nutanix文件 - “群集和文件服务器重命名”

Nutanix文件群集重命名在Nutanix文件2.1.1中引入，最低AOS版本为5.1.1。在最初的日子里，只有使用NCLI命令才有可能。

代码：

NCLI FS编辑名称= new_fs_name uuid =

从Nutanix文件3.0.0.1启用，可以通过Prism UI进行群集重命名。

脚步

选择文件服务器，然后单击更新标签。
选择文件服务器基础知识广播按钮并继续。

离开文件服务器域。
删除文件服务器DNS条目。
重命名文件服务器
加入文件服务器域

笔记：重命名文件服务器群集还将重命名FSVM。
FSVM的新名称将是“ ntnx - x”，其中'x'是FSVM编号。

2. Nutanix文件 - “文件服务器VM容量配置”

有时候，我们可能必须根据建议或增加负载来更新Nutanix文件服务器容量配置。由于它容易出现错误，因此我们不能再从Prism VM配置更新选项中直接更新FSVM容量。

选择文件服务器，然后单击更新标签。
选择文件服务器VM配置广播按钮并继续。

3. Nutanix文件网络配置更改：逐步

在引入AFS 3.0.0之前，Files网络配置（RE-IP）不受PRISM或CLI的支持，而是通过恢复PD（Local）快照的AFS来完成。它曾经起作用，但不是实现这一目标的一种非常优雅的方法。自3.0.0.1以来，我们有一种更优雅的方法来更改Nutanix文件网络配置。

工作流程

选择文件服务器，然后单击“更新”。
选择网络配置广播按钮并继续。
现在有一个选项可以更新客户端网络和存储网络。

支持以下网络更改：
单个Vlan to double Vlan
双Vlan到单个VLAN
托管网络到不受管理的网络
非托管网络到不受管理的网络

Unjoin域不是必需的。
客户需要在进行网络更改之前将DNS条目从Prism中解开。但是，这不是阻止要求，这意味着即使客户在更改之前没有登记DNS，我们也允许进行。

笔记：为了确保姓名分辨率可以正常工作，发布网络配置更改。Nutanix文件建议删除现有的文件服务器DNS条目并在发布网络配置后进行更新。

客户端和存储网络更改完成后，我们将获得一条流行消息，指出它是破坏性的。

如果用户尚未注册DNS条目，则需要对旧DNS条目进行手动清理。
帖子重新IP我们将发出警告，暗示未配置DNS条目。客户必须执行更新DNS一旦网络配置完成了

当DNS条目不是最新时，我们会生成一个警报。目前，我们每天做一次。如果启用了SMB或NFS，我们将验证A（正向）条目。如果启用了NFS，则验证PTR（反向）。如果两者都不启用，我们将不进行任何验证。

\r\n
\r\n

1. Nutanix Files - \"Cluster and File server Rename\"<\/b><\/h2>Nutanix Files Cluster rename was introduced in Nutanix Files 2.1.1 and minimum AOS version needed was 5.1.1. In the initial days, it was only possible using ncli command.
\r\n
code:<\/b>
ncli fs edit name=new_fs_name uuid=
<\/pre><\/div>
\r\n
\r\nFrom Nutanix Files 3.0.0.1 on-wards, the cluster rename can be done via Prism UI.
\r\n
\r\n
Steps <\/h3>
\r\n
Select File Server and click on the Update<\/b> tab. \r\n
Select File Server Basics<\/b> radio button and continue. \r\n<\/ul>
<\/a><\/p>
\r\n
\r\n
Leave the File Server domain. \r\n
Delete File Server DNS Entries. \r\n
Rename the File Server \r\n
Join the File Server domain \r\n<\/ul>
<\/a><\/p>
\r\n
Note:<\/b> Renaming the file server cluster will also rename the FSVM's.
\r\nNew name for the FSVM would be \"NTNX--x\" where 'x' is the fsvm number.<\/blockquote>
\r\n
\r\n
2. Nutanix Files - \"File Server VM capacity configuration\"<\/b><\/h2>
\r\nThere are times when we may have to update the Nutanix File Server Capacity Configuration based on recommendation or increase in load. We can no longer update the FSVM capacity directly from PRISM VM Configuration Update option since it was prone to errors.
\r\n
\r\n
\r\n
Select File Server and click on the Update<\/b> tab. \r\n
Select File Server VM Configuration<\/b> radio button and continue. \r\n<\/ul><\/a><\/p>
\r\n
\r\n
3. Nutanix File Network Configuration Changes: Step by Step<\/b><\/h2>
\r\nBefore AFS 3.0.0 was introduced, Files Network configuration ( Re-IP) was not supported feature from Prism or CLI but used to be done with workaround by restoring AFS from PD (local) snapshot. It used to work but was not a very graceful way to achieve this. Since 3.0.0.1, we have a graceful way to change the Nutanix Files Network Configuration.
\r\n
\r\n
<\/a><\/p>
\r\n
Workflow<\/b><\/h3> \r\n
Select the File Server and click on Update. \r\n
Select Network Configuration<\/b> radio button and continue. \r\n
Now there is an option to update Client Network and Storage Network. \r\n<\/ul><\/a><\/p>Following network changes are supported:<\/b>
\r\nSingle vlan to Double vlan
\r\nDouble vlan to Single vlan
\r\nManaged Network to Unmanaged Network
\r\nUnmanaged Network to Unmanaged Network
\r\n
\r\n
\r\n
Unjoin Domain is not a requirement. \r\n
Customer need to unregister DNS entries from prism before doing Network Changes. However, this is not a blocking requirement, which means we allow to proceed even if customers do not unregister DNS before making the changes. \r\n<\/ul>\r\n
<\/a><\/p>
\r\n
\r\n
Note :<\/b> To ensure Name Resolution works fine post the network configuration changes. Nutanix Files recommends to remove existing file server DNS entries and update it post the Network configuration is completed. <\/blockquote>
\r\n
\r\n
\r\n
\r\n
Once Client and Storage network IP changes are done, we have a pop message which points that it's disruptive. \r\n<\/ul>\r\n
<\/a><\/p>
\r\n
\r\n
If the user haven't unregistered DNS entries, manual cleanup of old DNS entries are required. \r\n
Post RE-IP we will have a warning implying that DNS entries aren't configured. Customer must perform UPDATE DNS<\/b> once Network configuration changes are done \r\n<\/ul><\/a><\/p>
\r\n
\r\n
We have an alert generated when DNS entries aren't up-to-date. Currently we do it once a day. We validate A (forward) entries if either SMB or NFS is enabled. PTR (reverse) are validated if NFS is enabled. If both are not enabled, we don't do any validation.<\/blockquote>","quoteUsername":"proyoung","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

喜欢

引用

分享

1回复

最古老的第一

新的先来最佳投票

o

OCCROB

旅行者

2个答复

1年以前
2020年3月3日

重命名过程确实更新了VM名称，但不会更新容器名称。如果您尝试重命名容器，则将其弄清楚，说明它在安装到主机时无法更改。但是，关闭所有关联的VM并卸载容器后，我仍然无法重命名它。

有没有办法可以重命名容器或迁移内容并指向新容器？

The renaming process does update the VM names, but it does not update the container name.\u00a0 If you try to rename the container, it is greyed out stating it cannot be changed while it is mounted to hosts.\u00a0 However, after shutting down all of the associated VMs and unmounting the container, I still cannot rename it.\u00a0<\/p>
\u00a0<\/p>
Is there a way to either rename the\u00a0container or\u00a0migrate the contents and point to a new container?<\/p>","quoteUsername":"OCCRob","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"}}}">

1. nutanix文件 - “群集和文件服务器重命名”

脚步

2. Nutanix文件 - “文件服务器VM容量配置”

3. Nutanix文件网络配置更改：逐步

工作流程

Workflow<\/b><\/h3> \r\nSelect the File Server and click on Update. \r\nSelect Network Configuration<\/b> radio button and continue. \r\n

回复

报名

登录社区

扫描病毒文件。

该文件无法下载