5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Hello @hienle You normally should be able to add the Hyper-V node to the cluster via Prism, and I recommend to sort out the problem there rather than follow the manual procedures. These articles may help:Cannot Discover New Nodes to Create Cluster or Add Nodes to existing Cluster DiscoveryOS: Cluster Expansion - Cannot add or discover nodes : IPMI console displays phoenix prompt Cannot Create Cluster or Add Nodes to Existing Cluster If you follow a manual process, please ensure you only add one node at a time because part of the process will be a domain join step for the Hyper-V node and this includes a reboot. In the automated domain join this will be done before the CVM is functionally joined to the cluster, but in a manual process if you reboot multiple active nodes for domain join this could cause impact. The discovery process is trying to find and connect with the foundation service on any unconfigured Nutanix node. A node should be discoverable for prism Expand Cluster proce
@Rominee you might be seeing the issue described in IPMI Java Console Fails to Open due to Connection Failed If you want to share the specific error you are getting I may be able to give a direct answer. I would suggest to try that KB article and see if the steps provided are able to resolve your issue. I do not normally encounter any issue. I click on the preview image of the console and get a “launch” file which opens in Java. That file has the network address and port, and a currently valid key which is tied to your IPMI browser session, so do not close that or log out when trying to open the console. So long as the port isn’t closed on the IPMI and you have a current version of the JRE installed on your workstation this normally should work. If you cannot get the Java console working but you have an up to date BMC firmware on your node, you should be able to use the html5 console and then mount the ISO from a neighboring CVM using the methods described at the KB linked in the la
Hello @Vignesh_Sk The Move VM disk is not created on the cluster. It can be downloaded from the portal as part of the ZIP file for AHV. As @PDAABI noted, the deployment instructions are in the documentation linked there. Please have a look and update here if you still have questions.
As noted in the document linked above, we cannot replace a G4 node with a G5 or later node in the same chassis. No such restriction exists at the cluster level, it’s just a question of mixing within the same physical chassis. Generally nodes in the same chassis should be homogenous, but varying RAM and disk capacity can be supported. From support the node type is tracked per-chassis so I would worry about keeping things straight getting replacement node from support if there is a difference between node models in the same chassis. It might need a notice on the account which can be placed by the account team. Your Nutanix SE should be able to answer any specifics for your current cluster.
Hello Pawarit, By itself the Files server does not provide an easy utility for this, but there is a method available. Have you looked into using File Analytics? For the information I think you’re looking for, I expect you can get this from the Audit Trails feature in File Analytics. This utility can be deployed by a Prism Admin and then can be used to review statistics and activity details on a Files server, including folder and file information on a per-user or per-share basis. The audit trails link above goes to the relevant section of the guide, while the first link goes to the download page for File Analytics. Please have a look and let me know if this answers your query. Thanks, JeremyJ
Hello balma01, If I understand you correctly, you describe you are seeing a false negative. You’re saying the check should give a failure but it does not. I think there is a misunderstanding here. Based on your description I think this is working as designed. The outcome of this check is not determined to be critical. If a default password is used the result given is an INFO. Only a WARN or FAIL result should change the check status from green to something else, yellow for WARN or red for FAIL. An INFO result is intended to show green. If you check the results, you should see an INFO note for components which still have a default password set. The details given from this check also link to the KB 6153 which describes the check and provdes methods for updating the passwords.
hello theGman, The primary document that *should* cover this is the Security Guide. The link there goes to the firewall recommendations. If you think something is missing there, please clarify. I can work with the documentation team, and security team if necessary, to close the gap. There is also this article “Port numbers used for inter CVM communication” which lists what services on the CVM use which ports. These do not all need to be open to the outside, many of them definitely should not be, so I only mention the KB as a knowledge reference. The firewall rules requirements, with explanation, should be in the security guide as I indicated earlier so if anything is missing there we can address it in that document. I think in writing the documentation, there is an expectation that Prism access would be from within the corporate network. You mentioned TCP 22 is needed for SSH, and 80 and 9440 are needed for accessing the web console. Is this is? or are there more ports that would
@Jose_orozco I understand you migrated the VM using Move 3.4.1. If you are using fully automated migration, Move should not start the migration before confirming VirtIO drivers are installed. This includes VirtIO drivers for disk, memory, and network. If you changed to manual mode you would need to ensure you installed the drivers yourself. Since you did not indicate there was any error reported from Move, I expect the Move server reported the migration was successful. Please clarify if I’m wrong. If you wanted to isolate whether this could be a disk driver issue, the steps to convert the virtual disk to IDE are in the KB “AHV | How to install VirtIO drivers for Microsoft Windows Server 2008” I’m guessing it may be something else, though I’m not sure what it would be since 2008 R2 is fully supported on AHV. ref: Compatibility Matrix If we had some more detail on what is seen from the BSOD, possibly we could come to a more definite answer. Share a screenshot here if you like, but I’d e
Normal methods to clear alerts would not work here since Prism, and NCLI which is just CLI interface to the same system, cannot list these alerts. I see a case was created for this. I think that is the best course of action here. The solution requires some manual editing that SREs normally would not do unassisted. Possibly a software fix can be produced from this so similar issues are not encountered in the future.
Hello ajeidani, I think the fault is not with Prism. The vm name shown there is a VM UUID. Please check if the VM exists on the host in a powered off state. SSH to the AHV host NTNX-3 and run “virsh list --all” and see if you find the VM there in a “shut off” state. If so, this is why Prism displays it. Under normal circumstances, a user VM will not exist in a powered off state on an AHV host. When the VM is powered off the configuration only exists in AOS. In your case I think there is some persisting information about this VM defined at the host even though the VM was powered off. Only the CVM has configuration built persistently at the host because it must be able to start before AOS services can start. No other UVM should continue to exist at the host when powered off. If you are seeing the VM in a “shut off” state at the host, it isn’t a matter of Prism displaying something that doesn’t exist. It’s a problem of a powered off user VM existing at the host. Normally you should not
This is not a known issue with an already-recognized root cause. You should not have to make any manual changes during conversion. I see a case is opened for this. I agree with that course of action. Much like the old method for replacing a failed hypervisor boot drive, it is possible to run a clean ESXi install, then download and use the phoenix iso and run “configure hypervisor” step. This does not complete any of the configuration steps for you so remaining procedures would need to be completed manually. If you have important VMs not yet registered on a successfully converted ESXi host, it may be better to troubleshoot the conversion process.
hello @kheraman Are you still having an issue? For successful application consistent VM snapshots, the following need to happen: Backup snapshot is triggered with app-consistent option enabled. The CVM reaches out to the NGT service running on the VM via TCP/IP to signal that VSS snapshot is needed. This requires TCP/IP communication be possible both ways, but should not need DNS since the NGT service will inform Prism of the IP, and the NGT installation has cluster IP info. (NAT could be a problem) The NGT service must, of course, be installed and running, and able to reach the CVM on port 2074. (more detail on what ports are needed for full NGT function here) Communication uses a pre-shared key which is part of NGT installation, and an identifier which is unique to the VM. To have this work, NGT installation must be unique per VM using the “mount iso” option from Prism. If cloning VMs, you can pre-install NGT and then mount the ISO again on the clone before powering on. The NGT serv
This kind of thing I would generally suggest to open a case for. A single restart or once in a long while is not much of a concern but if it is happening frequently we should be actively addressing this through a support case if possible. The stargate.FATAL message gives some insight but not many of these are user-serviceable.
Hi @Enterprise Compute At the risk of giving a similar answer, as of 5.16 there is not a supported method to backup/restore Prism Central, or export/import most Prism Central configuration. Security Policies (part of Flow) can be exported and imported, but that is partly because the security policy configuration is portable. The ability to create a configuration, export it once, and then import it in multiple ROBO sites was part of the original design. There has been a lot of work on this, but there are some remaining technical hurdles. I would definitely expect this to be well documented in the release notes and Prism Central Guide once we have a supported solution. I’m curious which configuration datasets you would most like to export and import.
@Thelmo Were you able to resolve the licensing issue using the information I provided? If not, let me know what is seen from the View Feature Violations details, and maybe share a screenshot of the create volume group UI box. I’d be happy to help further.
I think the solution you’re looking for is File Analytics. For a file server, human-readable logs of file operations (folder or file creation, by who and when) is usually unavailable or a debug only option simply due to the size of logs that would likely be created. With that in mind, if you want to get a look at when file operations happened and by who, we’re delving into metadata that wasn’t designed to be human readable as it stands on the server. Thankfully for situations like yours, our File Analytics offering includes an audit feature. Take a look at the guide here, I think this will meet the need you described:https://portal.nutanix.com/#/page/docs/details?targetId=File-Analytics-v2_1:File-Analytics-v2_1 Or to go directly to auditing, click here:https://portal.nutanix.com/#/page/docs/details?targetId=File-Analytics-v2_1:ana-fs-analytics-audit-trails-c.html
Hi @Thelmo You should be able to see the specific feature called out if you click on “View Licensing Details” or “View Feature Violations” in the red banner at the top of the Prism UI. reference: https://portal.nutanix.com/kb/3443 If the feature called out is “Nutanix Volumes” you’ve identified the issue correctly. The distinction is described in the Prism Web Console Guide, in the section for volume group configuration:https://portal.nutanix.com/#/page/docs/details?targetId=Web-Console-Guide-Prism-v510:wc-volume-group-configure-c.html Specifically this line: “iSCSI access to a volume group is provided through Nutanix Volumes. For more information, see Nutanix Volumes.” The alternative is using Volume Groups directly attached to VMs on AHV. This is only available on AHV. Using Volume Groups for VM storage on other hypervisors requires you to enable and establish external access using iSCSI (i.e. Nutanix Volumes). In practice, this correlates to the checkbox in VG creation “Enable
If I understand correctly, you’re wanting to get the “Open Connections” stat which is visible from Prism for a given File Server or share, and you want to fetch this using a REST API call or command. You’d also like to verify if this tells you the number of open sessions for a Files server. For day to day human-interactive operations, I’d recommend to use the MMC Snap-In for Nutanix Files, which includes the capability to list and manage SMB connections.https://portal.nutanix.com/#/page/docs/details?targetId=Files-MMC-Plugin-v3:Files-MMC-Plugin-v3 From your question though, it sounds like you’re wanting something you could script. I’m not sure of your use case but maybe one of these options will help. 1. Working from the CVM CLI, the command “ncli file-server list” will list Files servers on the cluster in detail. Part of this output is the “Total SMB Connections” stat. If you want details for just one Files server, you can use the ‘get’ command instead of list. syntax: ncli file-se
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.
