### Human: Can you tell about NCC Health Check: 10gbe_check. ### Assistant: The NCC health check 10gbe_check determines if there are any nodes in the cluster using 10GbE uplinks.. The NCC health check 10gbe_check determines if there are any nodes in the cluster using 10GbE uplinks.

The check reports a PASS status if one 10GbE NIC is found and CVM (Controller VM) is pinned to the 10GbE uplink. For best cluster operation, Nutanix CVMs communicate by using 10GbE network uplinks connected to a 10GbE wire-speed top of rack switch.

Note:For Dell, Nutanix supports only 10GbE NICs to be used for cluster traffic and imaging except XC640-4i model for 14G platforms. The option 1GbE NICs are recommended to be used for management purposes only and not for imaging or cluster traffic except for XC640-4i. 

The check results in a WARN status on AHV clusters when there are 1GbE and 10GbE NICs present in the bond.

The check results in a FAIL status if there are no 10GbE NICs detected on the hypervisor or nodes.

Running the NCC CheckRun the following check as part of the complete NCC Health Checks:

nutanix@cvm$ ncc health_checks run_all

Or run the following 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.

Sample outputFor Status: PASS

nutanix@cvm$ ncc health_checks run_all

For Status: INFO

nutanix@cvm$ ncc health_checks run_all

For Status: WARN

nutanix@cvm$ ncc health_checks run_all

For Status: FAIL

nutanix@cvm$ ncc health_checks run_all

For Status: ERR

nutanix@cvm$ ncc health_checks run_all

 

Note: Check ID 103073 (Check that CVM uplinked to an active 10Gbps link) has been retired from NCC 4.5.0. Make sure you are running the latest version of NCC before running the NCC health checks.Output messaging

Check ID6008DescriptionChecks whether CVM is uplinked to 10 GbE NIC.Causes of failureCVM not uplinked to 10 GbE NIC.			1 GbE NIC is part of the bond.			If the hypervisor is ESXi, it may be in lockdown.ResolutionsCheck network configuration.			If the hypervisor is ESXi, check for lockdown and unlock it.ImpactThe Controller VM is not configured to use the 10 GbE NIC or is configured to share the load with a slower NIC.Alert IDA1058Alert TitleCVM NIC Speed LowAlert MessageController VM service_vm_external_ip is running on the network interface(s) nic_list, with transmission speed less than 10 Gbps. This will degrade system performance.ScheduleThis check is scheduled to run every 5 minutes, by default.Number of failures to alertThis check will generate an alert after 1 failure.
Note : This hardware related check executes on the below hardware 
All Hardware except Inspur and SYS. Following are the steps to verify the uplinks manually at the hypervisor layer:

ESXiThe following procedure queries the uplink type in use on a Standard vSwitch or a Distributed vSwitch, depending on which vSwitch is handling inter-CVM communication.


	To manually verify the network uplink type currently in use, run this command from each ESX host:

	root@esxi# esxcfg-vswitch -l
	
	Verify that the uplinks in use for inter-CVM communication are 10GbE speed NICs.

	root@esxi# esxcfg-vswitch -l
	
	If 10GbE ports are in use and the check is still failing in ESXi, then confirm the CVM is assigned to the correct portgroup on the vSwitch and that the link is connected. This is done by going to vCenter, right-clicking on the CVM --> Edit Settings:

	

	If the Network label is blank or if the Connected checkbox is unchecked, the NCC check fails.

	To resolve, place the CVM in the correct port group and check the Connected check box.
	

For the INFO message (CVM is not uplinked to active 10Gbps NICs, but has a standby 10Gbps link), use vCenter or ESXi Web console to configure the vSwitch to have at least 1 active NIC. This should be done for all hosts that are mentioned in the alert.


	Log in to vCenter and click on the host that is showing the INFO alert. Go to the Configure tab. Select Virtual switches under Networking and select the vSwitch that has the adapters to which CVM connects (usually vSwitch0). Click the Edit button for that vSwitch

	
	
	Go to Teaming and failover and see the failover order. Everything should be under the standby adapter.

	
	
	Use the UP arrow key on the screen to move 1 or more vmnic to active adapters.

	
	Click OK.

Hyper-VVerify network speeds on each of the Hyper-V hosts from the CVM.

root@esxi# esxcfg-vswitch -l

Note: The Transmit and Receive Links speeds are from an LACP (twin NIC) configuration, resulting in the 20 GB aggregate values.

AHV


	Connect to CVM running on affected AHV host via SSH and run the following commands:

	root@esxi# esxcfg-vswitch -l
	
	In the output of commands mentioned above, make sure that br0 only contains NICs with speed 10000 or higher.

	Example:

	root@esxi# esxcfg-vswitch -l
	
	If 1Gb NICs are found in br0, perform the following steps to remove them:

	Note: The steps below are for AOS =< 5.19. To perform the process of removing 1G links for AOS 5.19 and newer, follow the Prism Web Console Guide for your associated AOS version under the section Creating or Updating a Virtual Switch (Example: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_19:wc-network-vs-create-upgrade-wc-t.html).

	Follow Verifying the Cluster Health chapter in the AHV Administration Guide to make sure that cluster can tolerate node being down. Do not proceed if the cluster cannot tolerate a failure of at least 1 node.Put the node and CVM in the maintenance mode:
		Check the availability of changing maintenance mode of target hosts:
			root@esxi# esxcfg-vswitch -l
			Put the host into maintenance mode - this will migrate running VMs to other hosts. If the cluster is a single-node cluster, UVMs should be shut down before executing following command:
			root@esxi# esxcfg-vswitch -l
			Enable maintenance mode for the CVM on the target host. This step is for preventing CVM services from being impacted by possible connectivity issues. You may skip this step if the CVM services are not running, or the cluster has stopped. If the cluster is a single-node cluster, you should skip this step because this CVM should not be put into maintenance-mode:
			root@esxi# esxcfg-vswitch -l

			Note: You can find <host ID> in the output of the "ncli host ls" command:

			root@esxi# esxcfg-vswitch -l
			
		Update br0 to only have 10G NICs:
		root@esxi# esxcfg-vswitch -l

		<bond mode> is one of the following modes: active-backup, balance-slb or balance-tcp. The current bond_mode can be found in the output of the manage_ovs show_uplinks command. If --bond_mode parameter is not specified, then the bond mode will be reset to active-passive, which may affect network connectivity.

		If LACP is used then a few more additional parameters should be added:

		root@esxi# esxcfg-vswitch -l

		Or specify NIC names manually:

		root@esxi# esxcfg-vswitch -l

		Note: On AOS 5.15 or later, due to a reliance on services that may be unavailable on the affected CVM during maintenance or network outage, manage_ovs may fail with output:

		root@esxi# esxcfg-vswitch -l

		To apply the required uplink changes, run the below command (with --host option targeting the host intended for an uplink change) from a different CVM which is in "UP" state and not in maintenance mode:

		root@esxi# esxcfg-vswitch -l
		
		Once the configuration is completed, make sure both hosts and CVM are accessible via network. Also, make sure that all NICs in the bond are operational by shutting down links one by one and verifying connectivity.
		
		If all tests are successfully completed, remove CVM and node from maintenance mode:

		From one of the other CVMs, run the following command to exit the CVM under maintenance mode:
			root@esxi# esxcfg-vswitch -l
			Exit host into maintenance mode - this will restore VM locality:
			root@esxi# esxcfg-vswitch -l
			
		
	

In case the steps or solution described in this article do not resolve the issue, 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.