5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
If your Nutanix infrastructure resides in an environment that includes an HTTP proxy, you’ll need to understand the HTTP proxy and proxy whitelist configurations in Prism. This is especially important if your cluster is registered to Prism Central. If the proxy setting and proxy whitelist are configured incorrectly, communication between PE and PC could be unreliable or entirely unusable. A note of clarification: in this post we discuss network communication inside and outside an environment. To prevent any confusion, the “environment” refers to the internal network, either physical local LAN, VLAN, or VPN, which is separated from other systems and the internet by a firewall and proxy. Anything within the environment is “local” and anything past the firewall is “external”. So, why does this matter? If your environment has an HTTP proxy there is probably also a firewall rule blocking any HTTP(S) traffic that is not going through the proxy. Without proxy configuration in this kind of env
There are various scenarios in which you may need to unregister a cluster from PC, and it is important to do it correctly. Whether you are decommissioning a Prism Element (PE) cluster which was registered to Prism Central (PC), or you already have decommissioned a cluster but it is still linked to a PC, or you have a cluster that is registered with one PC instance but would like to re-register it with a different PC instance for the benefit of localized management or to configure availability groups using Leap. All What does "correctly" look like? Done properly, unregistration of a cluster from PC involves a remove-from-multicluster step followed by clean-up of associated metadata. This metadata clean-up must be allowed to complete prior to attempting to re-register the cluster to a PC, otherwise, registration could be blocked. How to do it? There is no GUI method to unregister a cluster from Prism Central, so the process requires SSH access to the PC VM as well as to a CVM of th
Pulse is an essential tool for maintaining uptime on a Nutanix cluster. While alert emails can directly open a case for an issue which has already happened, the data gathered and sent by Pulse enables identification of potential known issues that haven’t impacted your cluster yet. Enabling this feature within a Nutanix cluster is fairly simple, but depending on your network setup and security there may be some additional steps to make sure it’s working. When you first set up your cluster, right around the time you accept the EULA and change the password for ‘admin’ you are given the option to disable Pulse. So long as you don’t select to disable it, Pulse will attempt to work with the default settings. For some environments it’s just that simple. The cluster will start sending data periodically to Nutanix and our Support Portal will highlight any concerns identified based on that configuration. The configuration is once-per-cluster. If you want to check or update your Pulse configu
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.