5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Some way I can buy you a beer?
Completed: Set Data Services IP Allowed iSCSI Services in the firewall on both servers (Strictly the existing iSCSI Inbound/Outbound rules, no new rules created or modified) Whitelisted the IQNs from both servers in the vGroup in Nutanix for Client Access Flushed DNS Rebooted each server that will be a member of the cluster Cleared and re-added the Data Services IP to verify it was saved down Attempted to connect the Windows VM to the Data Services IP via iSCSI Initiator Discover Portal using both the iSCSI Initiator and Default local adapter types Results: Connection Failed, no matter what variation of the above No ping the Data Services IP from any device No contact within iSCSI Initiator to the Data Services IP within the Discover Portal
I set the Data Services IP (it was blank) earlier this morning, around 9AM but I have yet to be able to get to it in any way. My 2 SQL boxes each say connection failure when attempting to connect to it. I thought it may be a DNS issue but I’ve flushed it on both machines and restarted one to be sure. I still cant ping it from any device though, so it still may be a DNS issue. Unsure. IP Examples: DataServices IP: 10.10.2.80 ServerA: 10.10.2.25 ServerB: 10.10.2.26 Any ideas?
I appreciate it, Izy. Just don’t want to mess this up. I am the new guy with this company, still in my 90 days. From the documentation: (This IP address is also used as a cluster-wide address by clients configured as part of Nutanix Files and other products. This IP address: Should be in the same subnet as the cluster Controller VM IP eth0 network interface addresses), Although none of ours seems to say Eth0, I assume it just means the actual IP on whatever interface I’m wanting to connect to. I should set it in the same subnet as my VM’s, correct? e.g.: Cluster - 10.10.10.100 VM1 - 10.10.110.100 VM2 - 10.10.110.101 In this case, I’d want the Virtual IP to be on the 110 subnet , correct?
I didn’t plan on changing anything else, just that field. Once I set it, that is what I set for the “Target IP” within the iSCSI initiator IP field?
This is kind of a huge warning. Almost terrifying. I want to make sure by setting the Data Services IP I’m not going to drop this cluster.
This Data Services IP address that you configured in Prism should be used. You can find more details on how to provide access the Nutanix storage from your clustered guest VMs here: https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v55:wc-cluster-details-modify-wc-t.html https://next.nutanix.com/installation-configuration-23/data-services-ip-iscsi-33804 As I stated above, the Data Services IP field is blank. It has never been set. I began setting it and it threw the warning “could potentially make the cluster unavailable” which I would of course like to not do.It may be a standard message when modifying a field on the Cluster Information screen, but I want to make sure I can change THAT field whenever I want and it wont harm anything (unless it’s being used, of course).
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
