rghosh8/supportGPT_data huggingface dataset:
### Human: Can you tell about Open Source Support. ### Assistant: This article describes how Nutanix supports open source repositories.. This article describes how Nutanix supports open source repositories.. OverviewNutanix is supportive of open-source technologies and leverages a community-supported model. Nutanix welcomes pull requests and responds to issues on a best-effort basis. Nutanix maintains public GitHub repositories for initiatives that help customers integrate the Nutanix platform with other third-party products. Support for these initiatives is handled directly via the GitHub repository. Issues and enhancement requests can be submitted in the Issues tab of each repository. Search for and review existing open issues before submitting a new issue.

RepositoriesThe Github repositories locations:

https://github.com/nutanixhttps://github.com/nutanix-cloud-native

Repositories include:

Ansible. Nutanix ansible collection nutanix.ncp is the official Nutanix ansible collection to automate Nutanix Cloud Platform (NCP). Location: https://github.com/nutanix/nutanix.ansibleCluster-API provider for Nutanix AHV. The Cluster API brings declarative, Kubernetes-style APIs to cluster creation, configuration and management. Cluster API Provider for Nutanix Cloud Infrastructure is a concrete implementation of Cluster API for Nutanix Cloud Infrastructure. Location: https://github.com/nutanix-cloud-native/cluster-api-provider-nutanixKubeflow. The Kubeflow project is dedicated to making deployments of machine learning (ML) workflows on Kubernetes simple, portable and scalable. Location: https://www.kubeflow.org/docs/distributions/nutanix/install-kubeflowTerraform. An infrastructure-as-code tool for building, changing and versioning infrastructure safely and efficiently. Location: https://github.com/nutanix/terraform-provider-nutanixPacker Plugin for Nutanix AHV. The Nutanix Packer builder is able to create Nutanix AHV virtual machine images and export them. Location: https://github.com/nutanix-cloud-native/packer-plugin-nutanix

The complete list of repositories:

https://github.com/orgs/nutanix/repositorieshttps://github.com/orgs/nutanix-cloud-native/repositories

Reporting an IssueTo report an issue:

Navigate to the specific GitHub repository and click on Issues. For example:

	
	Click New issue.
	
	Select Bug report or Feature request, then click the corresponding Get started button to the right.
	
	. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about NCC Health Check: check_cvm_ssh_security. ### Assistant: The NCC health check check_cvm_ssh_security checks whether the cluster uses Nutanix SSH security settings, such as lockdown and SSH security level.. The NCC health check check_cvm_ssh_security checks whether the cluster uses Nutanix SSH security settings, such as lockdown and SSH security level. This check was introduced in NCC 4.6.4.Running the NCC checkYou can run the check as part of the full NCC health check, as shown below.
nutanix@cvm$ ncc health_checks run_all
You can also run this check independently, as shown below.

nutanix@cvm$ ncc health_checks run_all
You can also run the checks from the Prism web console Health page: select Actions > Run Checks. Select All checks and click Run.

This check runs on Controller VMs only. It does not run on Prism Central.This check is scheduled to run every 24 hours, by default.This check will raise an NCC alert when a cluster does not use our SSH security settings, such as lockdown and SSH security level.
Sample Pass output:For Status: PASS

nutanix@cvm$ ncc health_checks run_all
If the check result is a PASS, Password-based remote login is not enabled. Everything is good.For Status: INFO

nutanix@cvm$ ncc health_checks run_all
If the check result is a INFO, Password-based login is enabled. It is recommended to not use password-based ssh login access to the cluster.Output messaging 
Check ID6219DescriptionCheck the strength of SSH security of the CVM.Causes of failureThe SSH security of the CVM is weak.ResolutionsChange the SSH security setting of the CVM.ImpactThe CVM's security might get compromised.ScheduleThis check is scheduled to run every 24 hours by default.Alert IDA6219Alert TitleThe cluster is using password based ssh access.Alert Smart TitleThe cluster is using password based ssh access for the cvm {cvm_ip} Alert MessageThe cluster is using password based ssh access for the cvm {cvm_ip} . Nutanix recommends using key-based ssh access to the CVM instead of password-based ssh access for better security. Refer to the Controlling Cluster Access section in the AOS Security Guide to set up key-based SSH access.Please perform the following actions to clear the INFO message in NCC:
Click the gear icon in the main menu and then select Cluster Lockdown in the Settings page.Disable remote login access by unchecking the Enable Remote Login with Password box. Refer Controlling Cluster Access.Click the New Public Key button and add Public Key for SSH access. Refer Controlling Cluster Access. Follow KB 1895 on how to set up password-less SSH Key pair.
Nutanix recommends avoiding ssh access to the CVM appliances as much as possible. Key-based SSH access is preferred instead of password-based access in the rare cases where one has to login to the CVM.Adding rsa/ecdsa public key will allow the admin and nutanix users to access CVMs and hosts using the ssh key pair.Note: Password-based SSH access will be deprecated in 2024.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about Under what conditions do Curator scans run?. ### Assistant: Lists the scenarios in which Curator Scheduled and Triggered scans are run.. There are two main types of Curator scans.
Scheduled Scans
	Curator Full ScanCurator Partial Scan
	Triggered Scans. Scheduled Scans
Scheduled scans run periodically on the cluster for the general maintenance of the system. There are two types of scheduled scans.


	Partial Scans

	Partial scans are responsible for performing the following tasks:

	Information Life Cycle Management (ILM)Snapshot chain severingDelete data that was marked to_remove but not dedupedCorrect block awarenessDelete or replicate over-replicated or under-replicated data

	By default, partial scans run 1 hour (3600 seconds) after the last partial scan completes.
	


	Full Scans

	In addition to all the Partial scan functions, Full scans also perform on-disk deduplication.	As only full scans perform on-disk deduplication, you might have to perform multiple scans to ensure that deduped data is deleted completely. Full scans run on their own timer and run 6 hours (21600 seconds) after the last Full scan completes. When this timer appears and if another scan is running, the timer waits for the scan to complete before running another Full scan.
	

Triggered Scans
Triggered scans respond to a situation in the cluster where Curator is urgently required.The most common triggered scans are as follows:

ILM - If the hot tier gets full, an ILM scan is triggered to drain some data to the cold tier.Disk Failure - If a disk fails, a scan is triggered to replicate the data having less replicas.Node Failure - This scan is similar to a disk failure scan, but runs to replicate data from all disks having had replica on the failed node.User - Manually triggered by the SRE team in certain situations. This can be a Full or Partial scan.
 These scans are all partial scans (unless the user manually triggers a full scan). They reset the clock on the next periodic partial scan (or full scan if it is a user triggered scan).. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about Upload of images larger that 16 Gb on AOS 5.20.2 or newer failing with "Image upload stream was interrupted" error. ### Assistant: Upload of images larger that 16 Gb on AOS 5.20.2 or newer failing with "Image upload stream was interrupted" error. Image uploads using Prism Element may fail with an "Image upload stream was interrupted" error if all of the following conditions apply:
Cluster is running AOS 5.20.2 or newer.The image file size is larger than 16 Gb.
The following stack trace may be found in /home/nutanix/data/logs/prism_gateway.log:

ERROR 2021-12-09 15:53:53,207Z http-nio-127.0.0.1-9081-exec-7 [] commands.acropolis.UploadImage.doExecute:405 java.net.SocketTimeoutException
 . This issue is resolved in:
AOS 5.20.X family (LTS): AOS 5.20.4AOS 6.5.X family (LTS): AOS 6.5.1
Please upgrade AOS to versions specified above or newer.WorkaroundUse From URL method.
Prepare a web server and share the image file via HTTP protocol.Select "From URL" as "Image Source" of "Image Configuration" and specify the URL to a disk file.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about Register for my.nutanix.com and Support Portal access. ### Assistant: Registering for my.nutanix.com Portal account and how to gain access to the Support Portal. The following article describes how to register for the my.nutanix.com Portal and access the Support Portal.. Please perform the following procedure to register for the my.nutanix.com Portal. Once successful you can then perform the additional steps to access the Support Portal. 
In the address bar of a web browser, type: https://my.nutanix.com and press EnterClick Sign up nowType the values of First Name, Last Name, Email, Password in the fields and click Submit	Note: Follow the specified password complexity requirements when you are creating the password	A confirmation page will be displayed and you will receive an email from mynutanix@nutanix.com after you have successfully completed the registration process. The following is an example of the email:

Hi First Name,

Click the link provided in the email to confirm the registration process. A message briefly appears in the browser confirming your email address and the my.nutanix.com Portal opens in the browser.Type the Email and Password that you used to register and click the arrow in the Password field. The my.nutanix.com Portal Welcome Back page appears.
For access to the Support Portal, continue with the following steps:

Select Support Portal and click the arrow in the Support Portal dialog box. Note: You must first activate the account before you can browse the Support Portal and create support casesIn the Activation Required dialog box that appears, enter the Business Email and a valid Nutanix Serial Number or Service Tag and click Activate. The Activation Complete! screen appears after you have successfully completed the activationClick the box next to I have read and agreed to the above terms and conditions to accept the terms. The Support Portal page will appear
If you are still experiencing access issues after following the steps above please contact portal-accounts@nutanix.com.Note: For access to the Partner Portal, there are 2 ways.

if your account does not have any assets or SW registration ID

Go to https://www.nutanix.com/partner-signup Fill out the Request Portal Access form and submit

If your account  has assets or SW registration ID

Click Activate on the Partner Portal tileFill out the Request Portal Access form and submit
Refer to the Partner team for any assistance with Partner Portal access. For help please send an email to partnerhelp@nutanix.com. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about "Cluster Memory Usage" widget may report inconsistent values on AHV cluster. ### Assistant: On the AHV cluster running AOS 5.15.1 or newer, "Cluster Memory Usage" widget may report inconsistent values.. On the AHV cluster running AOS version 5.15.1 or newer, "Cluster Memory Usage" widget may report inconsistent values.

Without an actual change in memory usage on a cluster, you may see the "Cluster Memory Usage" widget showing inconsistent values:

. This issue is resolved in:

AOS 5.15.X family (LTS): AOS 5.15.4AOS 5.19.X family (STS): AOS 5.19.1

Upgrade AOS to the version specified above or newer.

If upgrading to the previously mentioned versions doesn't resolve your issue, consider opening a case with Nutanix  support . ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about Alert - A160171 - FileServerTieredFileRestoreFailed. ### Assistant: Investigating FileServerTieredFileRestoreFailed issues on a Nutanix cluster.. This Nutanix article provides the information required for troubleshooting the alert FileServerTieredFileRestoreFailed for your Nutanix cluster.

After deleting a file server or a share, there could be files tiered referring to objects in the object-store. These objects could become stale if there are no references to them.

Nutanix recommends expiring these objects after the retention period configured for the object store profile.

Alert Overview

The FileServerTieredFileRestoreFailed alert is generated on share delete and FS delete operation.

Sample Alert

Block Serial Number: 16SMXXXXXXXX

Output messaging

Check ID160171DescriptionTiered File Restore Failed.Causes of failureTiered file restore failed unexpectedly.ResolutionsRefer to KB article 14507. Contact Nutanix support if issue still persists or assistance needed.ImpactTiered file is in inconsistent state.Alert IDA160171Alert TitleTiered File Restore FailedAlert Message{message]. Troubleshooting

The message from the alert will provide one of two reasons for failing to restore the file.

Scenario 1: "No object store configuration was found for profile." This means the profile was somehow deleted or not accessible.Scenario 2: When object was not found because it was deleted manually from object store or it was removed from object store as part of garbage cleaning.

Resolving the issue

Scenario 1: Contact Nutanix Support for assistance. See "Collecting Additional Information" below.Scenario 2: Attempt to undo the share-restore and try again with a newer snapshot.

Collecting additional information

Before collecting additional information, upgrade NCC. For information on upgrading NCC, see KB 2871.Run a complete NCC health_check on the cluster. See KB 2871.Collect Files related logs. For more information on Logbay, see KB-3094.
	CVM logs stored in ~/data/logs/minerva_cvm*NVM logs stored within the NVM at ~/data/logs/minerva*To collect the file server logs, run the following command from the CVM. Ideally, run this on the Minerva leader as there were issues seen otherwise. To get the Minerva leader IP on the AOS cluster, run:
		nutanix@CVM$ afs info.get_leader
		Once you are on the Minerva leader CVM, run:

		nutanix@CVM$ afs info.get_leader

		For example:

		nutanix@CVM$ afs info.get_leader
		
	

Attaching files to the case
To attach files to the case, follow KB 1294. If the size of the files being uploaded is greater than 5 GB, Nutanix recommends using the Nutanix FTP server due to supported size limitations.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about NCC Health Check: check_cvm_panics. ### Assistant: The NCC health check check_cvm_panics checks the CVM serial console log for panics.. The NCC health check check_cvm_panics checks the CVM (Controller VM) serial console log for panics and warns the user if the CVM has rebooted due to a panic recently. If a CVM panics, the panic output from the kernel is captured in the serial console log in the host in the NutanixCvmConsole event log.

Running the NCC check

This check will run as part of the full NCC health check:

nutanix@cvm$ ncc health_checks run_all

It can also be run as a standalone check:

nutanix@cvm$ ncc health_checks run_all

You can also run the checks from the Prism web console Health page: select Actions > Run Checks. Select All checks and click Run.

This check is not scheduled to run on an interval.

This check does not generate an alert.

Sample output

nutanix@cvm$ ncc health_checks run_all

Output messaging

Check ID106469DescriptionCheck if any CVMs have panicked.Causes of failureAt least one CVM panicked recently.ResolutionsFollow the instructions in KB 4379.ImpactStorage may have been unavailable while the CVM was restarting.. Determine current cluster state.

nutanix@CVM:~$ cs | grep -v UP

SSH to cluster and run confirm uptime.

nutanix@CVM:~$ cs | grep -v UP

SSH to the CVM which generated the alert and run the command last reboot to find the precise time of the panic.This alert references a brief event, rather than an ongoing state.  After this alert is triggered, the cluster usually returns to a healthy state.If the check fails, and the cluster is NOT in a healthy state (i.e. CVM down, services down, etc), contact Nutanix Support for additional diagnosis.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about cpupower frequency-info loads acpi-cpufreq driver instead of intel_pstate. ### Assistant: This article describes an issue where the command cpupower frequency-info loads acpi-cpufreq driver instead of intel_pstate.. This issue affects the following components combination:

Hardware: Intel Sapphire Rapids-based (SPR) nodes, including NX-G9AHV: 5.10.170-2.el7.nutanix.20220304.420.x86_64AOS: 6.5.3.1

SymptomsIn BIOS, the recommended setting for Hardware P-States is Disable by default on G9 SPR node.



In this case, cpupower frequency-info would use the acpi-cpufreq driver instead of the expected intel_pstate.

[root@host]# cpupower frequency-info

The turbostat command will continue to work when explicitly run.

This issue is caused by the intel_pstate driver being unable to retrieve CPU frequency values on SPR nodes. It requires support for SPR CPU set on AHV.. cpupower frequency-info using the acpi-cpufreq driver is a known behavior on SPR nodes.

Nutanix Engineering is aware of this behavior and is working on a fix to use the intel_pstate driver in a future release.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about Objects - Manual steps to configure emails for Objects Alerts. ### Assistant: Below are the steps to configure email notification for Objects Alerts. Currently, Prism Central does not show Objects Alerts and one can use the following workaround until Objects Alerts are integrated with Prism Central.. Customers using Nutanix Objects no longer receive notifications for Objects Alerts on Prism Central. They have to launch the Objects page from Prism Central and navigate to the Alerts page to view and take appropriate action based on alert severity. Below are steps to enable email notifications for Objects Alerts until they are integrated with Prism Central in future releases.Note: review the steps thoroughly before applying the workaround. If you have questions or concerns, contact Nutanix Support for assistance.. To set up email notifications, update the Alertmanager configuration presented to the Alertmanager Pod(s) as a Kubernetes secret on MSP cluster. Refer to KB-8170 for steps to access Objects cluster.Overall steps to configure email notifications:
Update the Alertmanager configuration with an appropriate template.Base64 encode the updated Alertmanager configuration.Update the YAML template containing the Alertmanager secret using the Base64 encoded value of the new configuration.Apply the secret on the MSP cluster.

Update the Alertmanager configuration with an appropriate template	Refer to the below YAML file and change the highlighted parameters as desired. The highlighted parameters will vary based on your environment. Save it as alertmanager.yaml.

	global:
	Base64 encode the alertmanager.yaml
	global:
	Generate secret from the YAML. Reference the below YAML file and change the highlighted parameter with the base64 encoded string. Save it as alertmanager-secret.yaml.
	global:
	Update the secret.	Copy over the alertmanager-secret.yaml to the MSP master and apply the configuration using the kubectl command:
	global:
	Verify if template is applied successfully to alertmanager container:
	global:

	global:
		After applying the secret successfully, you should start receiving emails for Objects Alerts based on template configuration.			         Fig 1: Email notification for Objects Alert	 Check if the emails can be sent: 	Review alertmanager logs to see if there are any issues sending emails:
	global:
		If there are issues similar to the above, test sending email to the SMTP server manually using telnet or netcat as described in KB 1638.		You can compare sending emails from PC or PE cluster if they are registered with the same SMTP server.
Template examplesBelow are a few examples of templates that can be used to configure email notifications based on your requirements. Refer Prometheus documentation for more details.

Receive an email for custom Alerts: 
	global:
	Receive customized email with formatting:
	global:
	Receive all email for all except few Alerts:
	global:
	Receive email for all Alerts:
	global:
	. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.
### Human: Can you tell about Files upgrades and FSM requirements. ### Assistant: Files requires upgrades of FSM to minimum versions.. Nutanix Files requires a component in AOS known as Files Server Module (FSM). The version of FSM required varies depending on the desired version of Files. Normally, this requirement is enforced during a Nutanix Files upgrade via Life Cycle Manager (LCM) or 1-click. This requirement can be circumvented if Nutanix Files 4.0.0.2 or higher is downloaded from the Nutanix Portal, and then uploaded manually to the Controller VMs (CVMs) for upgrade.. Nutanix Files 4.0.0.2 requires a minimum FSM version 2.1.1. Upgrade FSM to version 2.1.1 and above prior to upgrading.

Nutanix encourages the use of LCM for Files upgrades, which will enforce the proper FSM requirement.

To determine the version of FSM currently running, check LCM in Prism Element.



Should FSM show a version of 2.1.0 or earlier, then LCM is required to update FSM.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.