Cluster Init Page on Mac OS X
Anyone get the cluster_init page to work to setup a new block from their mac. I have done 4 or 5 installs and I never can get the page to come up. What am I doing wrong? How do I detect the IPv6 nodes online?
This topic has been closed for comments
Already have an account? Login
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Which browser are you using? Safari? FF? Chrome? all of `em?
Have you tried to connect to the IPv6 address directly, not the name?
I 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 ;)
I will post some troubleshooting steps from my history later on.
System preferences -> Network -> Select your interface -> Advanced -> TCP/IP Tab:
Like 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.
Next 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.
I 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.
That 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?
- Apple Bonjor service must be installed and running
- 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)
- IPv4 and IPv6 must be enabled
- Paste the CVM host name address with port :2100 appended to the hostname. Recommended browser is IE
Troubleshooting with Windows
- ipconfig /all is your friend
- Ping -6 ntnx-13am2k020104-a-cvm.local.%11
- Install DNS-SD browser on either Google Chrome or Firefox
- For the Ethernet port Enable IPv6 only
- Use Chrome or Firefox with the DNS-SD plugin to browse CVM Host name (remember to grab the trailing . after .local.)
- Paste the CVM host name address with port :2100 appended to the hostname. Recommended browser is Safari
Creating a Helper VM for VLAN’ed networks
To alleviate the issues of VLAN tagging and all of the confusion and problems with expanding the cluster VLAN’s pose, asking the customer to create a “Nutanix Helper” VM has been very helpful. This also eliminates the need to physically be in front of the Nutanix nodes to do the configuration.
Using 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.
During 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.
During 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.
Once the network ports are configured and Nutanix Servers are powered on you should be able to place the “Nutanix Helper VM” 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.
Now that you have the “Nutanix Helper VM” 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.
Note that you will have to connect to the “Nutanix Helper VM” through the VMware vCenter console as it typically will not be accessible because of the requirement of have an IPv4 autoconfiguration IP address.
Utilizing this configuration allows you to move the “Nutanix Helper VM” into different port groups to setup different clusters all around the world and is not dependent on a physical connection to the same switch.
Setting Native /default VLAN is the most important part if doing with the helper VM.
(Nutanix SE Midwest)
If you can reach cluster_init.html but aren't able to see any nodes discovered:
+ Try a couple of different browsers such as chrome, safari, firefox if possible
+ Check if the cvm is advertising with (you can ssh to the cvm via ipv6 or ipv4 if you have configured IPs)
nutanix@cvm_All NOS versions_$ ncli cluster discover-nodes
nutanix@cvm_NOS 3.5.3+_____$ discover_nodes
+ 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.
+ 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.
Hope that helps!