5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Your CVMs can upload log bundles directly to Nutanix for an open case, and this can speed case resolution especially if the alternative is the two-step process of pulling multiple GiB over WiFi to download and THEN upload. With common security restrictions around FTP or SFTP leaving the datacenter this may require explicit firewall rules. The logbay command to collect and upload logs looks like this: logbay collect --dst=sftp://nutanix -c <case_number> That destination “nutanix” isn’t helping us with that firewall rule, so where is the upload going? The software is really just automating the old manual methods described in this KB: Uploading Files for Nutanix Support Using FTP, SFTP or the Customer Portal. Referencing that article, we can see the DNS name for FTP uploads is ftp.nutanix.com . The IP address varies by region and might change, so I’d suggest using the URL. To allow log upload, you’ll need to allow port 22 for SFTP. You could also allow port 21 for FTP, but if it nee
When a Nutanix / vSphere cluster is deployed by Foundation the recommended drivers are installed, but after some time you may want to check if there is a newer driver recommended. From the Nutanix perspective, we have covered this with an NCC Health Check: esx_driver_compatibility_check so if you update NCC and run a health check, this check should tell you whether there is a later driver version qualified by Nutanix. To run the check from the CLI use “ncc health_checks hypervisor_checks esx_driver_compatibility_check” from any CVM in the cluster. You may see a newer driver listed for your NIC hardware and ESXi version. A newer driver may not have been qualified yet by Nutanix and in some cases could cause issues for the cluster, so generally we recommend staying with the recommended drivers as identified by NCC.
On a Nutanix cluster running VMware vSphere, you may be seeing this alert while there is no other sign of issue: Warning : Some storage containers have a high number of NFS files Impact : High number of NFS files may cause vpxa services on esxi hosts to restart. Cause : Number of files for respective storage containers has increased beyond 20K. This is expected with large VDI setups. Resolution : Reduce the number of files if you observe vpxa instability. Why do we see this alert? What needs to be done about it? As is noted on the relevant KB article this alert is set to be deprecated in an upcoming release of NCC. As suggested by the Impact and Resolution information above, the alert is related to a problem encountered in vpxa. The alert was created for an issue in vSphere 5.x that caused instability for the vpxa service if the number of files in a single NFS datastore was too high. The issue was resolved by VMware some time ago so you do not need to worry abou
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.