Replies posted by Nashma
Hello Carlo,Please navigate to the the Nutanix Support Portal >> Documentation >> Hardware Replacement Documentation (https://portal.nutanix.com/page/documents/list?type=hardware) and select Memory; filter out the desired hardware models using the drop-downs at the top right corner of the page. You can also find hypervisor specific documents.Please note that these are documents for Memory replacements, but you can use it for reseating as well.VM migration back to the affected node B again depends on your hypervisor settings and cluster workload as well. It is strongly recommended to place the host into maintenance mode for this activity.Cheers!
Hello Wei,Policies like Redundancy factor and Fault tolerance are often best implemented based on the setup, requirement and use-case of the environment and on a case by case basis. I would like to suggest you to go through this document: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_17:arc-failure-modes-c.html and decide which would suit better for your setup.You can focus on the Block awareness section of this document: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_17:arc-block-awareness-c.html and evaluate if it would be a good idea to move the fault tolerance domain to Block type.Cheers!
Hello Chetan, Hope Jonas’s response is helpful in clarifying your doubts.In furtherance to that, I would like to mention a few reference documents for more details or to help you with any follow up queries:For more details on protection domains: Data Protection and Recovery with Prism Element(P.S. For this particular query I would suggest Focus section: Configuring Data Protection with Asynchronous Replication and further)
Hello @Trey577 , It would be good if you could provide some more data. What is the use case behind this ask? Which Hypervisor and Guest OS are we talking about. This might help us in providing better answer to your request.Nonetheless, please check if the following documents help you with your requirement.Enabling serial port redirect on Nutanix Nodes How-to capture the serial output for a Linux VM on AHV
Hello @CarloNX,By default we use self-signed certificate, but it is recommended to replace the default supplied self-signed certificate with a CA signed certificate.Refer: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v5_15:sec-security-certificate-management-wc-c.htmlCheers!Nashma
@Sayo, Please confirm if you use VMware vShield or NSX in the environment?Also, Is the complete error message something like this: "Failed to get vlan tag of node: [ip]. Check if Expand Cluster workflow supports the node AOS version with VLAN setup."?Please log a case with our support team for further troubleshooting of this issue.
Hello @MichaelAhn! Could you confirm the hypervisor you are running on? Please share additional environment details like PC version, Cluster(AOS) version, Hypervisor version etc. Did you recently perform any activity like hypervisor conversion, PC upgrade etc? Additionally, where is the Prism Central VM deployed? Is it on the clusters managed by this PC or on different environments. Cheers! Nashma
@SEdge, If you haven’t set the name for your Prism Element you can check out this document to edit the cluster name from the GUI: https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v5_15%3Awc-cluster-details-modify-wc-t.html#task_bhg_yqp_rn If you would like a CLI reference, check out ‘Edit params of a Cluster’ section of this link: https://portal.nutanix.com/page/documents/details/?targetId=Command-Ref-AOS-v5_15%3Aacl-ncli-cluster-auto-r.html Let me know if you need additional assistance. Cheers!
Hello @Brian.Cabral, Do you still have the issue? Please provide the below details: When was the last upgrade done on the Prism Central? How many clusters are registered on this Prism Central? Please share the version environment details of those clusters as well. Do you see any issues launching the other clusters? Could you confirm If you can you extract and share a logbundle from your setup? Cheers!
Hi @roadstone, It is not recommended to remove these crash files if they are not older than 3 months! That said, if you have received the analysis for the issue and wish to clear files, you can clear them as normal files. Make sure you don’t delete the /var/crash directory. Yes, run a complete NCC checks post clearing these.
Hi @Welsper Most firmware updates through LCM are run from a CentOS-based staging area called Phoenix. reboot_to_phoenix is an API used to enter this stage and invoke the upgrade activities in this stage. Similarly, reboot_to_host, is later used to exit this staging area and boot the upgraded node back into its hypervisor after firmware upgrades. In your situation, the API had issues in post upgrade phase and hence you see the firmwares reflect the latest versions despite the error thrown on the LCM activity. In such situations, we reboot the host into hypervisor and bring the host and CVM out of maintenance mode.
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.