rghosh8/supportGPT_data huggingface dataset:
### Human: Can you tell about Alert - A130348 - VmInPausedState. ### Assistant: NCC 4.2: This Nutanix article provides the information required for troubleshooting the alert "VM is in Paused state" for your Nutanix cluster.. This Nutanix article provides the information required for troubleshooting the alert "VM is in Paused state" for your Nutanix cluster.Alert OverviewThe "VM is in Paused state" alert is generated when the Acropolis service detects a VM in Paused state. This is an unexpected VM state which should not be seen during daily operations.Sample Alert
Warning: VM found in paused state.
Potential ImpactVM is not operational.Output Messaging 
Check ID130348DescriptionVM found in paused state.Cause of FailureFailed migration or some hypervisor issue.ResolutionsPower cycle the VM to get it out of this state.ImpactVM in paused state most likely means downtime and it's in an irrecoverable state.Alert Smart TitleVM {vm_name} with ID {vm_uuid} has been found in paused stateAlert TitleVM is in Paused stateAlert MessageVM {vm_name} with ID {vm_uuid} has been found in paused state. TroubleshootingPower Off the affected VM and then power it On to recover. Contact Nutanix Support at https://portal.nutanix.com as soon as possible to fully troubleshoot the problem. Collect additional information and attach them to the support case.

Collecting Additional Information

Before collecting additional information, upgrade NCC. For information on upgrading NCC, see KB-2871.Collect the NCC output file ncc-output-latest.log. For information on collecting the output file, see KB-2871.Collect Logbay bundle using the following command. For more information on Logbay, see KB-6691.

nutanix@cvm$ logbay collect --aggregate=true

If the logbay command is not available (NCC versions prior to 3.7.1, AOS 5.6, 5.8), collect the NCC log bundle instead using the following command:

nutanix@cvm$ logbay collect --aggregate=true
Attaching Files to the CaseAttach the files at the bottom of the support case on the support portal.If the size of the NCC log bundle being uploaded is greater than 5 GB, Nutanix recommends using the Nutanix FTP server due to supported size limitations. See KB-1294.Requesting AssistanceIf you need further assistance from Nutanix Support, add a comment to the case on the support portal asking Nutanix Support to contact you. If you need urgent assistance, contact the Support Team by calling one of our Global Support Phone Numbers. You can also click the Escalate button in the case and explain the urgency in the comment, and Nutanix Support will be in contact.Closing the CaseIf this KB resolves your issue and you want to close the case, click on the Thumbs Up icon next to the KB Number in the initial case email. This informs Nutanix Support to proceed with closing the case. You can also update the support case saying it is okay to close the case and Nutanix Support will close the case.. ### 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 Pre-upgrade check: Hypervisor Upgrade (test_host_upgrade_versions_compatible). ### Assistant: This pre-upgrade check runs during hypervisor upgrades. It checks if the base and target ESX versions are upgrade compatible.. test_host_upgrade_versions_compatible is an ESXi pre-upgrade check that runs during hypervisor upgrade. It checks whether the base and target ESXi versions are upgrades compatible. The reason for this check is that ESXi introduced a new certificate for VIB signing into the trust store in 2018 to begin the transition from the old certificate (which expired on 31st December 2019).

Error messages generated on UI by this check:

"Current host version %s and the target host version %s are not compatible for upgrade". VMware recommends upgrading ESXi hosts to a minimum of the builds (listed below), which were released after March 2018 and have the newer signing certificate in the trust store. Doing so prevents future installation and upgrade failures due to the untrusted signing certificate:
6.0 ESXi600-201807001 (Build: 9239799) or later 6.5 U2 (Build: 8294253) or later6.7 GA (Build: 8169922) or later.

The upgrade should be retried using a compatible ESXi release (above). Once upgraded to a compatible build, you may upgrade to the target release version. For all ESXi build numbers and versions, refer to VMware KB 2143832.VMware has addressed this issue in VMware KB 76555.For any queries consider engaging 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 Nutanix Files - File and folder permissions. ### Assistant: Configure Nutanix Files Admin and default permissions for a home and general purpose shares.. It may be difficult to determine user permissions without access to Active Directory (AD). If there are issues with share access or domain joining because of permissions, and you are certain that there are no issues with connectivity, follow the steps below to verify if the logged-in user has AD user privileges.. Execute the following command on Windows SMB Client to retrieve a list of groups of which the logged-in user is a member. Any user that is a member of the BUILTIN\Administrators group (most of the time, Domain Admins) should be able to access the share.

PS C:\Windows\system32> whoami /groups /FO list

Sample output:

PS C:\Windows\system32> whoami /groups /FO list

Default Permissions for Nutanix Files SharesThere are two share types: distributed and standard. In the example output below, nufs-sec-smb1 is a distributed share while nufs-sec-smb2 is a standard share.

PS C:\Windows\system32> whoami /groups /FO list

Look at the default permissions of these shares (from the client machine). In the example output below, the named directory UserJohn is the TLD (top-level directory) at the root of the distributed share.

PS C:\Windows\system32> whoami /groups /FO list

PS C:\Windows\system32> whoami /groups /FO list

PS C:\Windows\system32> whoami /groups /FO list

The same permissions can be checked using icacls or Explorer.

In Nutanix Files 3.0 and later, a user or a group can be added as a File Server Admin/Backup Admin in Files user interface. Alternatively, use the ncli fs add-admin-user command.

 

Get files/directories authorization information.From Nutanix Files version 3.8 onwards there is a new CLI introduced to query files and directories authorization information. 

PS C:\Windows\system32> whoami /groups /FO list
In the following example, a user named "Admin" is unable to access the folder "users" in the share "Eng". Use the following steps in order to validate the permissions or authorization for a user named "Admin" in the folder "users".1. SSH into any FSVM2. List current ACL set on a share and folder. In this example, it is share "Eng" and folder "users". In the output below, AD user "Admin" has set explicit DENY ACL in the "users" folder.

PS C:\Windows\system32> whoami /groups /FO list. ### 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 Lazan service restarts unexpectedly due to non-ASCII characters in VM disk names. ### Assistant: Lazan service restarts frequently due to non-ASCII characters being present in the VM name/VMDK files on the cluster after upgrading to AOS 6.5.x or 6.0.x. Lazan service restarts frequently due to non-ASCII characters in the VM name/VMDK files on the cluster after upgrading to AOS 6.5.x or 6.0.xThe following alert is generated:
One or more cluster services have restarted within 15 minutes in the PCVM/CVM, the total restarts being >= 10. The following are the service(s) that have restarted : ['lazan'].
The Following CRITICAL error signature can be seen in the /home/nutanix/data/logs/lazan.out logs:

One or more cluster services have restarted within 15 minutes in the PCVM/CVM, the total restarts being >= 10. The following are the service(s) that have restarted : ['lazan'].. This issue is resolved in:
AOS 6.5.X family (LTS): AOS 6.5.3
Please upgrade AOS to versions specified above or newer.Engage Nutanix Support at https://portal.nutanix.com/ to recover the cluster.. ### 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: hwclock_check. ### Assistant: The NCC health check hwclock_check verifies hardware clock functionality and any time differences.. The NCC Health Check hwclock_check checks if the hardware clock is healthy. It checks the date from the real-time clock (hardware clock) on the hypervisor against the date of the Controller VM (CVM).Time differences in the hardware clock and system clock can cause problems. The hardware clock operational check ensures that the hardware clock is functional.

Running the NCC CheckYou can run this check as part of the complete NCC Health Checks:

nutanix@cvm$ ncc health_checks run_all

Or you can run this check separately:

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 scheduled to run every 10 minutes, by default.

This check will generate an alert after 5 consecutive failures across scheduled intervals.

Sample output
For Status: FAIL

nutanix@cvm$ ncc health_checks run_all
For Status: PASS

nutanix@cvm$ ncc health_checks run_all

Output messaging

DescriptionCheck if the Hardware clock has failedCauses of failureThe RTC clock on the host has failed, or the RTC battery has died.ResolutionsReplace the node. Refer to the Nutanix documentation for instructions.Alert TitleHardware Clock FailureAlert MessageHardware clock in host host_ip has failed.

Note: This hardware-related check executes on the below hardware

Nutanix NXDell XCHPELenovo HXNutanix SXFujitsu XFLenovo SRPoweredgeIntelIBMHyveVoyager TDC. This NCC check or alert for the hardware clock can be raised for the following reasons:
Network failure between the NTP server and the host.The system clock and hardware clock on the host are incorrect.Incorrect time on the NTP server.The RTC is powered by the same battery as the CMOS. This battery may have expired, or the RTC clock on the host has failed.

If this check fails, consider engaging  Nutanix Support. Additionally, gather the output of ncc health_checks run_all and attach it to the support case. . ### 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 PC Cluster Runway/Scenarios not working on NCC 3.7.1/3.7.1.x. ### Assistant: Due to ENG-225071, cluster runway or new scenarios may stop working when you upgrade to NCC 3.7.1 or 3.7.1.x prior to upgrading PC. You can work around the issue by reinstalling NCC.. Scenario#1 Due to a known issue, Prism Central or Cluster Runway scenarios may stop working. This happens when a customer upgrades to NCC 3.7.1 or NCC 3.7.1.1 in advance before upgrading Prism Central to PC 5.10.3.x. You may notice the following symptoms:

Cluster Runway is showing N/a instead of data.Cluster Runway shows, "We are currently collecting usage data. Cluster usage data will be displayed here in 24 hours." for an extended period (longer than 24 hours)."RPC error kTransportError raised" is seen when creating a new scenario.
Scenario#2

The same issue is reported on pc.2022.1, where the Neuron server is continuously crashing, because of which the Capacity planning feature does not work.As per recent instances, the issue may get resolved by upgrading PC to latest version i.e 2022.1.0.2 and a fix for this is also tracked in above mentioned tickets.. Scenario#1:

Long-term fixes for this issue are included in AOS 5.10.4, AOS 5.11, and NCC 3.7.2. Upgrade to AOS 5.10.4, 5.11 or later, and to NCC 3.7.2 or later.A workaround for this issue is to reinstall NCC manually on Prism Central and then wait for 24 hours for data to populate. Instructions for this are available on the portal; for example, this link for 5.10 https://portal.nutanix.com/page/documents/details?targetId=Acropolis-Upgrade-Guide-v5_18:ncc-ncc-install-t.html.

Scenario#2:

The issue is resolved in pc.2022.9, pc.2022.6.0.1, pc. 2023.1.0.1. Please upgrade to those releases for the fix.

 . ### 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 Support during a critical upcoming upgrade/maintenance. ### Assistant: Support during a critical upcoming upgrade/maintenance. Can Nutanix Support join a customer in a call to guide them and provide coverage during critical upcoming activities? Nutanix SREs are often expected to engage in customer remote sessions for installation, upgrades or configuration activities during their maintenance window.

While Nutanix Support would always like to be available for our customers, we are not equipped to handle requests related to installation, upgrades or configuration. If we remain on a remote session for the duration of such an activity, then we become unavailable to address critical break/fix issues.

Nutanix Support's primary responsibility is addressing and troubleshooting customer break/fix issues, not handling other maintenance activities.. Nutanix prides itself on providing robust tools and documentation to facilitate maintenance activities such as installation, upgrades, etc. We highly recommend leveraging these resources. The Acropolis Upgrade Guide outlines the steps and resources needed for such activities.

Use the Life Cycle Manager (LCM) to upgrade all or some of the software and firmware components. In the event LCM cannot be used, use the Legacy 1-click method from the Web Console.

Ensure that all the prerequisites of maintenance activity are met. It is possible that during the maintenance, you exhaust all the documentation (both KB articles and guides) and still require assistance from a Nutanix SRE. These instances may be, but are not limited to, the following situations:

An installation/upgrade is stalledAn installation/upgrade completes but one or more nodes do not come upIntermittent service crashesInter/intracluster connectivity issuesNetwork/storage unavailability or instability

In the event assistance is still needed, the best way to get support is to raise a case via the Support Portal.. ### 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 - A111066 - Failed to send alert Emails. ### Assistant: This Nutanix article provides the information required for troubleshooting the alert: "Alert E-mail Failure" for your Nutanix cluster.. Alert Overview

The Alert E-mail Failure alert can be generated due to:

Errors in email-alerts scriptError while executing email-alerts scriptErrors while creating an email file for the alert

Check ID111066DescriptionFailed to send alert emails.Causes of failureAlert is raised if a Controller VM is unable to send an alert email.ResolutionsEngage Nutanix Support.ImpactAlerts notification emails will not be sent.Alert TitleAlert E-mail FailureAlert MessagesUnable to send alert E-mail from Controller VM {service_vm_external_ip} due to “E-mail client error”. Capture alert manager service logs, email-alerts.log, and send-email.log from all the CVMs in the cluster. Open case with Nutanix Support and attach the log files to the case.Log files location:
~/data/logs/alert_manager.out~/data/logs/email-alerts.log~/data/logs/send-email.log 
To collect these logs using the Logbay tool and upload them to the support case:

logbay collect -t alerts,email --dst=ftp://nutanix -c <case number>
For more information about the log collection tool Logbay, please refer to KB-6691.Note: If the alert persists in Prism UI. Please try disabling and re-enabling in the Health page in Prism.In Prism select Health from menu. To find the alert select the Checks tab on right hand side of page. Then search for "Alert E-mail Failure". Click 'Turn Check Off,' then 'Turn Check On' to clear its status.. ### 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 Frozen I/O State in Microsoft SQL Server During application-consistent snapshots. ### Assistant: MSSQL databases can remain frozen indefinitely during application-consistent snapshots.. 


During the creation of application-consistent snapshots, there is a possibility of encountering a problem that can cause Microsoft SQL Server (MSSQL) databases to become frozen. This issue specifically occurs during VSS-based backups, where the MSSQL databases can remain frozen indefinitely. 



In MSSQL Logs, the error logs will show as below (The logs can be obtained by following this Microsoft article)

2023-05-18 23:48:52.79 spid77     I/O is frozen on database [DATABASE_NAME]. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

Obtain the Microsoft SQL version the UVM is running to confirm if this KB applies.Method 1:Connect to the instance of SQL Server, and then run the following query:

2023-05-18 23:48:52.79 spid77     I/O is frozen on database [DATABASE_NAME]. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

The result of running the query above would be the following:

2023-05-18 23:48:52.79 spid77     I/O is frozen on database [DATABASE_NAME]. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

Method 2:Another way of checking the version is by connecting to the instance of SQL Server, and then run the following query in SQL Server Management Studio (SSMS):

2023-05-18 23:48:52.79 spid77     I/O is frozen on database [DATABASE_NAME]. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

The result of running the query above would be the following:

2023-05-18 23:48:52.79 spid77     I/O is frozen on database [DATABASE_NAME]. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.. This is a known issue (reported in MS KB-4523102) detected by Microsoft on SQL databases that contains memory-optimized filegroup and VSS based backups. Microsoft has released the following cumulative updates for SQL Server:

Cumulative Update 2 for SQL Server 2019 (Build version: 15.0.4013.40)Cumulative Update 19 for SQL Server 2017 (Build version: 14.0.3281.6)Cumulative Update 10 for SQL Server 2016 SP2 (Build version: 13.0.5492.2). ### 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 NDB might get an alert about Nutanix cluster connectivity during a cluster upgrade. ### Assistant: When a software or firmware upgrade is performed on the Nutanix cluster, NDB can generate an alert about the cluster connectivity.. During a software or firmware upgrade on the Nutanix cluster, NDB can generate an alert about the cluster connectivity status:
Health check failed for cluster (name:<Cluster_Name>), Please make sure the cluster is in valid state
The era_server.log on the NDB server will have the following entry:
Health check failed for cluster (name:<Cluster_Name>), Please make sure the cluster is in valid state
 . If the alert is generated during an upgrade activity, it is expected and can be safely ignored as long as the cluster connectivity status goes back to normal when the upgrade is completed.To check the cluster connectivity status: NDB -> Administration -> Nutanix clusters.The reason why it happens is because during most of the upgrades, the CVMs reboot in a rolling manner and the virtual IP address gets re-hosted from the Prism leader CVM to a different CVM. That can take a few seconds, so the virtual IP can be briefly unavailable, which causes the API checks coming from the NDB to fail and it is enough to generate the alert in NDB.. ### 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: stale_recovery_points_check. ### Assistant: The NCC health check stale_recovery_points_check checks if there are any recovery point entries in the Insights database whose underlying snapshots have been deleted.. The NCC health check stale_recovery_points_check checks if there are any recovery point entries in the Insights database whose underlying snapshots have been deleted.It can be run as part of the complete NCC check by running 
nutanix@cvm:~$ ncc health_checks run_all
or individually as:

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 scheduled to run every 12 hours, by default.This check will generate an alert after 2 failure.

Sample outputFor status: PASS

nutanix@cvm:~$ ncc health_checks run_all
For Status: ERROR

nutanix@cvm:~$ ncc health_checks run_all
 

Output messaging

Check ID110405DescriptionChecks if there are any recovery point entries in the Insights database whose underlying snapshots have been deleted.Causes of failureThe snapshot was deleted without removing the associated stale entries in the Insights database.ResolutionsCheck the running status of the Polaris service.ImpactUpcoming replications might be impacted by the stale remnant entries in the Insights database.
 . If this NCC check fails, engage Nutanix Support.Additionally, gather the following command output and attach it to the support case:  
nutanix@cvm:~$ ncc health_checks run_all
 . ### 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 Lose local attach vDisks after adding a NIC. ### Assistant: After adding the second NIC to Windows Server, non-bootable local attach vDisks disappear from within guest OS. After adding the second NIC to Windows Server, non-bootable local attach vDisks disappear from within guest OS. Only drive C is present.Migrating or Rebooting the VM does not solve the issue. . Open disk management in windows and check the disks should be marked as offline.To bring the disks online, right click on each vdisk and click "Online". Now you should be able to see and use the vdisks within guest OS.. ### 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 OVA UI may take longer to load due to unreachable Prism Element cluster registered to Prism Central. ### Assistant: When connected clusters are unreachable the OVA UI may take longer to load. OVA UI may take longer to load if one or more registered Prism Element clusters are unreachable.
The /home/nutanix/data/logs/aplos.out log file on Prism Central will contain the following error:

2023-01-06 02:18:40,257Z ERROR resource.py:231  Traceback (most recent call last):
You may also notice the following RPC timeouts in the logs: 
2023-01-06 02:18:40,257Z ERROR resource.py:231  Traceback (most recent call last):

 . Prism Central tries connecting to every connected Prism Element cluster to check compatibility.To find the unreachable Prism Element UUID, you can refer to the below logs:
2023-01-06 01:45:22,964Z WARNING fanout_protobuf_rpc.py:230 Error # 5 sending RPC [500] to http://127.0.0.1:9444/v3/fanout_proxy?remote_cluster_uuid=0005eea4-b61d-36d5-408d-7cc255078170&url_path=remote_rpc_requ
If the Prism Element cluster is deleted without properly unregistering, refer to KB 4944 to clean the Prism Element cluster details.. ### 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.