Mac OS X上的集群Init页面

V
徽章 ＋６
任何人都可以使用cluster_init页面来从他们的mac上安装一个新的块。我已经安装了4或5次，但我从来没有得到这个页面。我哪里做错了?如何在线检测IPv6节点?

    13日回复

    mluksch
    Userlevel 2
    徽章 + 10
    我想那是我，因为我没有mac;)

    您使用的是哪种浏览器?旅行吗?FF吗?铬吗?所有的他们?

    你是否尝试直接连接到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链路本地启用)-确保，您即将使用的节点接口有一个链接，并在同一vlan比您的主机-名称解析工作“自动”感谢“bonjour”协议。MacOS:启用per default ->检查窗户:安装iTunes /你好Linux如果NTNX——NODEID-CVM.local，则安装avahi(发行版特定)。:2100不工作:1.尝试ping它:ping6 NTNX——NODEID-CVM.local。-> ping6 works => problem is@browser(见下面)-> ping6不工作=>问题别处=> goto 2。2.测试你自己的ipv6: Linux / MacOSX:#查找你的IP ifconfig | grep inet6 - >如果没有返回,你没有特定接口上启用ipv6 # ping它ping6 #多播萍(1包)ping6往上平移- ff02:: 1 - >现在至少你的主机应该#再次回答,多个数据包停止用ping6我ff02:: 1 - >至少现在,你应该收到更多的主机的答案，取决于你的网络上的IPv6主机回答多播请求(大多数是这样，nutanix也一样)窗户: -使用ping而不是ping6 -不需要- i开关，现在要么尝试修复/调试名称解析(A)，或(B)通过其IP地址直接访问一个Nutanix cvm(一)调试名称解析-为bonjour/avahi配置本地/个人防火墙?-在没有防火墙的情况下试试Linux: #浏览所有类型“nutanix”avahi-browse _nutanix_tcp - >空?试一试:#浏览所有IPv6 bonjour记录avahi-browse规律| grep IPv6——>如果你可以看到设备/主机,但没有nutanix,很可能一些防火墙阻塞bonjour之间,或节点/ avahi服务有一个“问题”#的完整性/(上电后我这条线/重新塑造的节点)#当然,这只在i在b c d中是“OK”的情况下才有效;完成MacOSX: dns-sd -B _nutanix。_tcp #我猜也有一个应用程序(图形化)窗户: http://support.apple.com/kb/ht2703(B)直接ping一个nutanix节点->我们将需要获得IPv6地址手册-连接到Hypervisor，并从那里到CVM (vmware: viclient / KVM: virt-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)-start它#通过解析它自己的主机名来检查它:#这应该工作的肯定-> avahi-浏览_nutanix。_tcp #你应该看到每个节点2次(IPv4和IPv6)浏览器—> disable proxy if set—> Firefox: about:config—> network.dns。禁用ipv6应该是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
    徽章 ＋６
    我要试试这个。我可以在已经初始化的块上测试这个吗?是否有测试页面?
    J
    排名
    徽章 ＋７
    如果集群已经初始化，则集群初始化页面将被重定向。如果你不能让cluster_init页面按照预期工作，请在下次安装时打开支持案例。
    mluksch
    Userlevel 2
    徽章 + 10
    正如Jerome所说，cluster_init.html应该重定向到cluster_status.html(一旦您连接的节点是集群的一部分)
    G
    徽章 ＋２
    只要确保你的vlan/交换机上的igmp snooping是关闭的。
    basraayman
    排名
    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上的大多数浏览器更喜欢IPv4而不是IPv6(只是谷歌)。通过这种方式，我可以确保它不是一个浏览器问题，因为尝试使用IPv4解析DNS上的链接本地地址。

    我通常使用Safari作为cluster_init页面的浏览器，因为它与OSX紧密耦合，并且似乎有最好的Bonjour集成。Chrome在这方面做得不太好，以前有一个单独的Chrome插件叫做DNSSD (DNSSD .me)，但现在已经不再发布了，尽管你仍然可以在网上找到版本。

    在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
    • 你可以打开IPv6仅通过DNS-SD发现，但如果你尝试做。local的名称解析。Bonjor不能正确解析.local。并导致错误。您必须启用IPv4以允许。local。决议
    —IPv4必须有一个自动配置的IP地址....169.254.x.x
    • 如果你被分配了一个DHCP IPv4地址，它会失败，因为你不是在同一个子网的Nutanix节点[list]
    • 需要注意的是，通过cluster destroy销毁的集群将保留IPv4地址。如果是这种情况，您将需要在相同的IPv4广播域。
  • 如果启用了DHCP IPv4地址和它没有autoconfigure IP仅仅改变静态和配置169.254.100.100地址与255.255.0.0子网掩码[/列表]——使用Chrome或Firefox DNS-SD插件浏览CVM主机名(记得抓住落后。后。local)。
    —在主机名后面粘贴“CVM主机名address with port:2100”。推荐使用IE浏览器。


    故障排除与Windows

    ipconfig /all是你的朋友
    • 确保你的IPv4地址是169.254.x。x地址
    • 请注意在下面的例子中，本地链接地址后面列出的适配器编号是%11
    -
    - Ping -6 ntnx-13am2k020104-a-cvm.local.%

    苹果

    —在谷歌Chrome浏览器或Firefox浏览器上安装DNS-SD浏览器
    —对于以太网端口，只启用IPv6

    -使用Chrome或Firefox与DNS-SD插件浏览CVM主机名(记住抓住尾随。后。local)。
    —在主机名后面粘贴“CVM主机名address with port:2100”。推荐浏览器为Safari



    为VLAN化网络创建Helper虚拟机

    为了缓解VLAN标签的问题以及扩展集群VLAN的姿态所带来的所有混乱和问题，要求客户创建一个“Nutanix Helper”VM是非常有帮助的。这也消除了在Nutanix节点前面进行配置的需要。

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

    在网络预安装期间，询问网络团队他们将分配ESXi主机和Nutanix Controller VM的VLAN。一般情况下，这些端口在同一个VLAN中，并且端口设置为Trunk。对于本例，网络团队希望ESXi主机和Nutanix CVM在VLAN 100中。
    在讨论期间，询问网络团队是否能够将VLAN 100设置为他们将用于Nutanix的特定集群端口的默认VLAN。说明通过设置默认VLAN, ESXi主机管理和Nutanix Controller将在相应的VLAN中。这也允许无缝扩展。如果他们继续使用适当的默认VLAN扩展来放置新的Nutanix节点，只需单击一次即可。如果不设置缺省VLAN，则必须手动分配VLAN标签，增加了扩展的复杂性。

    一旦网络端口配置好，并且Nutanix服务器上电，您应该能够放置“Nutanix Helper VM”，它运行在用户环境中的某个ESXi主机上，以工作在一个端口组上，该端口组上有VLAN ID 100标记。

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

    注意，您必须通过VMware vCenter控制台连接到“Nutanix Helper 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
    我使用辅助虚拟机。把一个新的区块发送到一个网站，然后告诉他们把它插进去，这样就容易多了，我可以在任何地方配置这个区块。
    T
    排名
    Userlevel 2
    徽章 + 13
    我同意Josh，这周我正在部署320个节点，所有这些都是通过一个辅助虚拟机完成的。数据中心在几英里之外。也更舒适。

    如果使用辅助虚拟机，设置本机/默认VLAN是最重要的部分。

    托尼
    (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"}}}">
    米
    徽章 ＋３
    大家好，Mac版的Bonjour浏览器帮助我获得了节点的链接，所以我可以在安装期间用任何浏览器登录。https://www.macupdate.com/app/mac/13388/bonjour-browser
    V
    徽章 ＋６
    Bonjour浏览器…好了!
    克里斯蒂
    排名
    徽章 ＋６
    如果发现cluster_init.html有问题，可以尝试以下几个故障排除技巧

    如果你可以到达cluster_init.html，但不能看到发现的任何节点:
    +如果可能的话，尝试几个不同的浏览器，如chrome, safari, firefox

    +检查cvm是否发布(如果你配置了ip，你可以通过ipv6或ipv4 ssh到cvm)
    nutanix@cvm_All NOS versions_$ ncli cluster discovery -nodes
    nutanix@cvm_NOS 3.5.3 + _____ discover_nodes美元

    +如果你不能看到cvm看到自己的discover_nodes，那么cvm不是广告，可能会有不同的问题。这种情况有时会出现在以前可能从集群中删除的节点上。

    +如果discovery -nodes/discover_nodes工作，但cluster_init.html没有，那么你可能想要连接你的计算机/辅助虚拟机到本地子网，以排除任何防火墙问题。

    希望会有帮助!
    \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"}}}">

    回复


    Baidu