Mac OS X上的群集初始页面

v
徽章 +6
任何人都会获取cluster_init页面来工作以从其Mac设置新块。我已经完成了4或5个安装，我永远无法让页面出现。我究竟做错了什么？如何在线检测IPv6节点？
    该主题已关闭以供评论

    13个答复

    mluksch
    UserLevel 2
    徽章 +10
    我以为是我，没有Mac;）

    您正在使用哪个浏览器？苹果浏览器？ff？铬合金？所有的em？

    您是否尝试过直接连接到IPv6地址，而不是名称？

    我认为主要的问题是，我们大多数人对IPv6的经验不够，一旦插件不起作用，我们注定要失败；）
    稍后，我将从历史记录中发布一些故障排除步骤。
    \n
    \nWhich browser are you using? Safari? FF? Chrome? all of `em?
    \n
    \nHave you tried to connect to the IPv6 address directly, not the name?
    \n
    \nI think the main problem is that most of us just aren't experienced enough with IPv6, and as soon as the plug&play doesn't work, we are doomed ;)
    \nI will post some troubleshooting steps from my history later on.","quoteUsername":"mluksch","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    mluksch
    UserLevel 2
    徽章 +10
    - 首先，请确保您遵循“设置指南”中的准则。（如果在主机上禁用IPv6链接启用IPv6，请启用IPv6） - 确保您即将使用的节点接口具有链接，并且与您的主机相同的VLAN中，由于“ Bonjour”协议，该名称分辨率“自动”工作。苹果系统：启用每个默认值 - >检查视窗：安装iTunes/bonjourLinux：安装avahi（特定于分销）如果ntnx-nodeid-cvm.local.:2100不起作用：1.尝试ping：ping6 ntnx-- nodeid-cvm.local .-> ping6 works =>问题是@Browser（请参见下文） - > ping6不起作用=>其他地方=> goto 2。2.“测试”您自己的IPv6： Linux/MacOSX：＃查找您的IP IFCONFIG |GREP INET6->如果什么都没有返回，则在特定界面＃ping it ping6＃多播Ping（一个数据包）ping6 -c1 -i ff02 :: 1->现在至少您的主机应该回复＃的特定接口＃ping6＃ping6＃ping6＃ping6＃ping6＃ping6＃ping6＃ping6＃ping6＃ping6＃同样，有多个数据包使用ping6 -i ff02 :: 1->至少现在，您应该收到比您的主机更多的答案，具体取决于网络上的IPv6主机，回答了多播请求（大多数也可以，nutanix也是如此）视窗： - 使用ping代替ping6-不需要-i切换现在尝试修复/调试名称分辨率（a），或（b）直接通过其IP地址访问Nutanix CVM之一（a）调试名称分辨率- 为Bonjour/Avahi配置的本地/个人防火墙？- 无防火墙尝试Linux：＃浏览所有类型的“ nutanix” avahi -browse _nutanix._tcp->空？尝试：＃浏览所有IPv6 Bonjour记录Avahi -Browse -Alr |GREP IPv6->如果您可以在这里看到设备/主机，但是没有Nutanix，则可能是在两者之间进行某些防火墙，或者是阻止Bonjour，或者节点/他们的Avahi服务有一个“问题”＃for Polotinentys/for Polotinentys/in Pointerentys/in Pointerentys/i（我之后，我是那个行节点的电源上的电源）＃当然，只有在a b c d中的i可以“正常”;做avahi resolve -6 -n ntnx-$ {i} -cvm.local。完毕macOSX：dns -sd -b _nutanix._tcp＃我想也有一个应用程序（图形）视窗：http：//support.apple.com/kb/ht2703（b）直接ping nutanix节点- >我们将需要获取IPv6地址手册 - 连接到管理程序，然后从那里连接到CVM（VMware：viclient / kvm：firt -manager） - 内部CVM：ip -6 addr show eth0 |grep inet6 # afaik its always eth0 (ymmv) try to ping it now (see above) -> if unsuccessful -> ask your network/fw/switch admin -> if ping works, access the IPv6 IP in the browser, but beware, you need to put the IPv6 address into square brackets, like: http://[fe80::5054:ff:fe96:2fb2]:2100/cluster_init.html3. KVM检查- >服务avahi-daemon状态＃如果不运行，（re） - 启动＃通过解决自己的主机名： - > avahi-resolve-host-name`hostname`.local''。＃这应该可以肯定工作 - > avahi -browse _nutanix._tcp＃您应该看到每个节点2次（ipv4＆ipv6）浏览器- >禁用代理如果设置 - > firefox：关于：config-> network.dns.disableipv6应该是false--> chrome：没有特定的设置？- > Safari：没有特定的设置？- > ie：没有特定的设置？当然，与仅使用IPv4-Address相比，所有这些可能太耗时了（如果知道），但是这样做一次，您可能会一直发现自己在做错了什么
    MacOS<\/b>: enabled per default -> check Windows<\/b>: install iTunes\/bonjour Linux<\/b>: install avahi (distribution-specific)if NTNX--NODEID-CVM.local.:2100 is not working:1. try to ping it:<\/u><\/b>ping6 NTNX--NODEID-CVM.local.-> ping6 works => problem is@browser<\/b> (see below)-> ping6 doesn't work => problem elsewhere => goto 2.2. \"test\" your own ipv6:<\/u><\/b> Linux\/MacOSX<\/b>: # look up your IP ifconfig | grep inet6 -> if nothing is returned, you do not have ipv6 enabled on the specific interface # ping it ping6 # multicast ping (one packet) ping6 -c1 -I ff02::1 -> now at least your host should have replied # again, more than one packet stop it with ping6 -I ff02::1 -> at least now, you should have received answers from more hosts than yours, depending on IPv6 hosts on your network answering multicast requests (most do, nutanix too) Windows<\/b>: - use ping instead of ping6 - no need for -I switch now either try to fix\/debug the name resolution (A), or (B) access one of the Nutanix CVMs via its IP address directly(A) debug name resolution<\/b> - local\/personal firewall configured for bonjour\/avahi? - try it without firewall Linux<\/b>: # browse all of the type \"nutanix\" avahi-browse _nutanix._tcp -> empty? try: # browse all IPv6 bonjour records avahi-browse -alr | grep IPv6 -> if you can see devices\/hosts here, but no nutanix, chances are that either some Firewall in between is blocking bonjour, or the nodes\/their avahi service have a \"problem\" # for completeness \/ (i that line after power on \/ reimageing of nodes) # of course, this works only if things are \"OK\" for i in a b c d;do avahi-resolve -6 -n NTNX--${i}-CVM.local.; done MacOSX<\/b>: dns-sd -B _nutanix._tcp # i guess there is an app for that (graphical) too 😉 Windows<\/b>: http:\/\/support.apple.com\/kb\/ht2703(B) ping a nutanix node directly<\/b> -> we will need to get the IPv6 Address manual - connect to the Hypervisor and from there to the CVM (vmware: viclient \/ KVM: virt-manager) - inside the CVM: ip -6 addr show eth0 | grep inet6 # afaik its always eth0 (ymmv) try to ping it now (see above) -> if unsuccessful -> ask your network\/fw\/switch admin 😉 -> if ping works, access the IPv6 IP in the browser, but beware, you need to put the IPv6 address into square brackets, like: http:\/\/[fe80::5054:ff:fe96:2fb2]:2100\/cluster_init.html3. KVM check<\/b> -> service avahi-daemon status # if not running, (re)-start it # check it by resolving its own hostname: -> avahi-resolve-host-name `hostname`.local. # this should work for sure -> avahi-browse _nutanix._tcp # you should see every node 2 times (IPv4 & IPv6)Browser<\/b> -> disable proxy if set -> Firefox: about:config -> network.dns.disableIPv6 should be false -> Chrome: no specific settings? -> Safari: no specific settings? -> IE: no specific settings?Of course all of that might be too time-consuming compared to just use the IPv4-Address (if known), but do it once, and you might discover what you are doing wrong all the time 😉","quoteUsername":"mluksch","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    v
    徽章 +6
    我要尝试一下。我可以在已经初始化的块上测试吗？有测试页面吗？
    j
    秩
    徽章 +7
    群集初始页面将被重定向，如果群集已经初始化。如果您无法获得预期的cluster_init页面，请在下一个安装上打开支持案例。
    mluksch
    UserLevel 2
    徽章 +10
    正如Jerome所说，cluster_init.html应该重定向到cluster_status.html（一旦您连接到的节点是群集的一部分）
    G
    徽章 +2
    只需确保您的VLAN/SWITCH上的IGMP窥探即将到来。
    巴士莱曼
    秩
    Userlevel 1
    徽章 +15
    只是为了跟进这里，请确保在Mac上，您设置了IPv6链接本地地址：

    系统首选项 - >网络 - >选择您的接口 - >高级 - > TCP/IP选项卡：
    http://next.nutanix.com/t5/image/serverpage/image-id/100ib540a8e5b93e0d54/image-size/original?v=mpbl-1&px=-1

    就像mluksch（我如何在答复中标记一个名字？）说，请确保您在同一子网/VLAN中，并且您的开关不会丢弃IPv6链接本地流量。

    我通常要做的下一件事就是仅在界面上禁用IPv4，而仅使IPv6链接 - 本地地址保持活跃。原因相对简单。Mac上的大多数浏览器都比IPv6更喜欢IPv4（仅Google为此）。这样，我可以确保它不是试图使用IPv4在DNS上解析DNS上的链接本地地址引起的浏览器问题。

    我通常将Safari用作cluster_init页面的浏览器，因为这与OSX紧密结合，并且似乎具有最好的Bonjour集成。Chrome做得不好，曾经有一个称为DNSSD（dnssd.me）的Chrome的单独插件，但这不再发布，尽管您仍然可以在线找到版本。

    在99％的案件中，这对我有用。完成cluster_init零件后，不要忘记重新打开IPv4。如果有人有兴趣，我还可以尝试在我的个人博客上放置视频？
    \n
    \nSystem preferences -> Network -> Select your interface -> Advanced -> TCP\/IP Tab:
    \nhttp:\/\/next.nutanix.com\/t5\/image\/serverpage\/image-id\/100iB540A8E5B93E0D54\/image-size\/original?v=mpbl-1&px=-1<\/a>
    \n
    \nLike mluksch (how the heck do I tag a name in a reply?) said, make sure you are in the same subnet\/VLAN, and that your switch isn't dropping IPv6 link-local traffic.
    \n
    \nNext thing I usually do is just disabling IPv4 on my interface and only keep the IPv6 link-local address active. The reason for that is relatively simple. Most browsers on Mac prefer IPv4 over IPv6 (just google for that). This way, I can make sure that it isn't a browser problem caused by trying to resolve the link-local address on the DNS using IPv4.
    \n
    \nI usually use Safari as the browser for the cluster_init page, since this is tightly coupled in to OSX, and seems to have the best Bonjour integration. Chrome doesn't do this that well, there used to be a seperate plugin for Chrome called DNSSD (dnssd.me), but that is no longer being published, although you can still find versions online.
    \n
    \nThat does the trick for me in 99% of the cases. Don't forget to switch IPv4 back on after you are finished with the cluster_init part. I can also try to put a video doing this on my personal blog if anyone is interested?","quoteUsername":"basraayman","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    t
    秩
    UserLevel 2
    徽章 +13
    使用Nutanix自动发现

    视窗

    -Apple Bonjor服务必须安装并运行
    -DNSSD浏览器插件是可选的（可以轻松进行故障排除，如果节点未通过DNS-SD浏览器发现，则无法使用自动发现）
    -IPv4和IPv6必须启用
    • 您只能通过DNS-SD打开IPv6进行IPv6，但是如果您尝试执行.Local的名称分辨率。Bonjor将无法正确解决.Local。并导致错误。您必须使IPv4启用。解析度
    -IPv4必须具有一个自动配置IP地址….169.254.x.x
    • 如果您被分配了DHCP IPv4地址，它将失败，因为您与Nutanix节点[list]不在同一子网上
    • 一个警告是在一个通过群集销毁销毁的集群上保留IPv4地址。如果是这种情况，您将需要在同一IPv4广播域中。
  • 如果在IPv4地址上启用了DHCP，并且没有AutoConfigure IP简单地更改为静态和配置169.254.100.100地址，则使用255.255.0.0 subnet mask [/list] - 将Chrome或firefox与DNS-SD插件一起使用，浏览CVM主机名（请记住要抓住尾随。
    - 将CVM主机名地址粘贴到端口：2100附加到主机名中。推荐的浏览器是IE


    Windows故障排除

    - ipconfig /all是你的朋友
    • 确保您的IPv4地址为169.254.x.x地址
    • 记下在本地链接地址之后列出的适配器编号，在下面的情况下为％11
    -
    -ping -6 NTNX-13AM2K020104-A-CVM.LOCAL。％11

    苹果

    - 在Google Chrome或Firefox上安装DNS-SD浏览器
    - 对于以太网端口仅启用IPv6

    - 将Chrome或Firefox与DNS-SD插件一起浏览CVM主机名（请记住要抓住尾随。
    - 将CVM主机名地址粘贴到端口：2100附加到主机名中。推荐的浏览器是Safari



    为VLAN的网络创建辅助VM

    为了减轻VLAN标记的问题以及扩大群集VLAN姿势的所有困惑和问题，要求客户创建“ Nutanix Helper” VM的VM非常有帮助。这也消除了在Nutanix节点前进行配置的必要性。

    使用指南的Windows部分中定义的设置要求客户创建VM 2008R2或Windows 7并安装所需的插件。Bonjor，Firefox或Chrome和DNS-SD插件。

    在网络预构图期间，询问网络团队他们将要分配ESXI主机和Nutanix控制器VM哪个VLAN。通常，它们在同一VLAN中，端口设置为中继。在此示例中，网络团队希望ESXI主机和Nutanix CVM在VLAN 100中。
    在此讨论中，网络团队是否可以将VLAN 100设置为默认的VLAN，以用于将其用于Nutanix使用的特定中继端口。解释说，通过设置默认的VLAN ESXI主机管理和Nutanix控制器将处于适当的VLAN中。这也允许无缝扩展。如果他们继续将新的Nutanix节点放置在适当的默认VLAN扩展中，那么单击就像单击一样容易。如果不设置默认VLAN，则必须手动分配VLAN标签并为扩展增加复杂性。

    一旦配置了网络端口并将Nutanix服务器供电，您应该能够将正在运行的“ Nutanix Helper VM”放置在用户环境中的某个地方，以在具有VLAN ID 100标记的端口组中工作在上面。

    现在，您拥有“ Nutanix助手VM”，ESXI主机和CVM都在同一VLAN 100广播域中，您可以使用Chrome或Firefox浏览器启动设置，以查看DNS-SD主机名。

    请注意，您必须通过VMware Vcenter控制台连接到“ Nutanix辅助VM”，因为它通常无法访问，因为需要具有IPv4自动配置IP地址。

    利用这种配置使您可以将“ Nutanix Helper VM”移动到不同的端口组中，以设置世界各地的不同群集，并且不依赖于与同一开关的物理连接。
    • Auto discovery with Nutanix<\/b>
    \n
    \nWindows<\/u><\/b>
    \n <\/u><\/b>
    \n- Apple Bonjor service must be installed and running
    \n- DNSSD browser plugin is optional (makes for easy troubleshooting, if nodes do not discover via DNS-SD browser you will not be able to use autodiscover)
    \n- IPv4 and IPv6 must be enabled
    \n
      \n
    • You can turn on IPv6 only for the discovery via DNS-SD but if you try to do name resolution of the .local. Bonjor will not properly resolve the .local. and cause an error. You must have IPv4 enabled to allow for .local. resolution<\/ul>- IPv4 must have an autoconfigure IP address\u2026.169.254.x.x
      \n
        \n
      • If you are assigned a DHCP IPv4 address it will fail as you are not on the same subnet as the Nutanix Nodes[list] \n
      • One caveat to this is on a cluster that was destroyed via Cluster destroy will retain the IPv4 addresses. If that is the case you will need to be in the same IPv4 broadcast domain.<\/ul>\n
      • If DHCP is enabled on the IPv4 address and it does not have a autoconfigure IP simply change to static and configure a 169.254.100.100 address with a 255.255.0.0 subnet mask[\/list]- Use Chrome or Firefox with the DNS-SD plugin to browse CVM Host name (remember to grab the trailing . after .local.)
        \n- Paste the CVM host name address with port :2100 appended to the hostname. Recommended browser is IE
        \n
        \n
        \nTroubleshooting with Windows<\/u><\/b>
        \n <\/u><\/b>
        \n- ipconfig \/all is your friend
        \n
          \n
        • Make sure your IPv4 address is a 169.254.x.x address \n
        • Make note of the adapter number which is listed after Local Link address in the case below it is %11<\/ul>-
          \n- Ping -6 ntnx-13am2k020104-a-cvm.local.%11
          \n <\/b>
          \nApple<\/u><\/b>
          \n <\/b>
          \n- Install DNS-SD browser on either Google Chrome or Firefox
          \n- For the Ethernet port Enable IPv6 only
          \n
          \n- Use Chrome or Firefox with the DNS-SD plugin to browse CVM Host name (remember to grab the trailing . after .local.)
          \n- Paste the CVM host name address with port :2100 appended to the hostname. Recommended browser is Safari
          \n
          \n
          \n
          \nCreating a Helper VM for VLAN\u2019ed networks<\/u><\/b>
          \n <\/u><\/b>
          \nTo alleviate the issues of VLAN tagging and all of the confusion and problems with expanding the cluster VLAN\u2019s pose, asking the customer to create a \u201cNutanix Helper\u201d VM has been very helpful. This also eliminates the need to physically be in front of the Nutanix nodes to do the configuration.
          \n
          \nUsing the setting defined in the Windows portion of the guide ask customer to create a VM 2008R2 or Windows 7 and install the required plugins. Bonjor, Firefox or Chrome and DNS-SD plugin.
          \n
          \nDuring the network preinstallation ask the network team which VLAN they were going to assign the ESXi host and the Nutanix Controller VM. Typically these are in the same VLAN and the ports are set to Trunk. For this example the network team wishes the ESXi host and Nutanix CVM to be in VLAN 100.
          \nDuring this discussion ask the network team if they would be able to set VLAN 100 as the default VLAN for the specific trunked ports that they are going to use for the Nutanix. Explaining that by setting the default VLAN the ESXi host management and Nutanix Controller will be in the proper VLAN. This also allows for seamless expansion. If they continue to place the new Nutanix nodes with the proper default VLAN expansion is as easy as a single click. Without setting the default VLAN you must manually assign the VLAN tags and adds complexity to expansion.
          \n
          \nOnce the network ports are configured and Nutanix Servers are powered on you should be able to place the \u201cNutanix Helper VM\u201d that is running on an ESXi hosts somewhere in the users environment to work off of a port group that has the VLAN ID 100 tagged on it.
          \n
          \nNow that you have the \u201cNutanix Helper VM\u201d and the ESXi hosts and CVM all in the same VLAN 100 broadcast domain you can start the setup using the Chrome or Firefox browser to see the DNS-SD host names.
          \n
          \nNote that you will have to connect to the \u201cNutanix Helper VM\u201d through the VMware vCenter console as it typically will not be accessible because of the requirement of have an IPv4 autoconfiguration IP address.
          \n
          \nUtilizing this configuration allows you to move the \u201cNutanix Helper VM\u201d into different port groups to setup different clusters all around the world and is not dependent on a physical connection to the same switch.","quoteUsername":"tonyholland00","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Joshsinclair
    秩
    UserLevel 2
    徽章 +13
    我使用助手VM。将新块发送到站点并告诉他们将其插入的位置更加容易，然后我可以在任何地方配置块。
    t
    秩
    UserLevel 2
    徽章 +13
    我同意乔什（Josh），本周我正在部署320个节点，所有这些节点都是由助手VM完成的。数据中心距离英里。也更舒适。

    设置本机 /默认VLAN是使用辅助VM的最重要部分。

    托尼
    （Nutanix SE中西部）
    \n
    \nSetting Native \/default VLAN is the most important part if doing with the helper VM.
    \n
    \nTony
    \n(Nutanix SE Midwest)","quoteUsername":"tonyholland00","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    m
    徽章 +3
    大家好，Mac的Bonjour浏览器帮助我获得了指向节点的链接，因此我可以在设置过程中使用任何浏览器登录。https://www.macupdate.com/app/mac/13388/bonjour-browser
    v
    徽章 +6
    Bonjour浏览器....很好！
    克里斯蒂
    秩
    徽章 +6
    如果您看到cluster_init.html的问题，您可能会尝试一些故障排除技巧

    如果您可以到达cluster_init.html，但看不到发现的任何节点：
    +尝试几个不同的浏览器，例如Chrome，Safari，Firefox

    +检查CVM是否正在使用广告（如果您配置IPS，则可以通过IPv6或IPv4 ssh到CVM）
    nutanix@cvm_all nos版本_ $ ncli群集发现节点
    nutanix@cvm_nos 3.5.3+_____ $ discover_nodes

    +如果您看不到CVM与Discover_nodes看到自己，那么CVM不是广告，并且可能存在不同的问题。有时可以通过以前可能从群集中删除的节点可以看到这一点。

    +如果Discover-Nodes / Discover_nodes有效，但是cluster_init.html却没有，那么您可能需要将计算机 /辅助VM连接到本地子网以排除任何防火墙问题。

    希望有帮助！
    \n
    \nIf you can reach cluster_init.html but aren't able to see any nodes discovered:
    \n+ Try a couple of different browsers such as chrome, safari, firefox if possible
    \n
    \n+ Check if the cvm is advertising with (you can ssh to the cvm via ipv6 or ipv4 if you have configured IPs)
    \nnutanix@cvm_All NOS versions_$ ncli cluster discover-nodes
    \nnutanix@cvm_NOS 3.5.3+_____$ discover_nodes
    \n
    \n+ If you cannot see the cvm see itself with discover_nodes then the cvm is not advertising and there may a different issue. This is sometimes seen with nodes that have been possibly removed from a cluster previously.
    \n
    \n+ if discover-nodes\/discover_nodes works but cluster_init.html does not then you may want to connect your computer \/ helper VM to the local subnet to rule out any firewall issues.
    \n
    \nHope that helps!","quoteUsername":"christie","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