### Human: Can you tell about LCM not listing all available Redfish updates on nodes and might show "System does not meet Redfish requirements". ### Assistant: LCM does not list all of the available Redfish on the nodes due to the internal interface not being reachable, and shows "System does not meet Redfish requirements" for one or more nodes.. A new issue has been identified in LCM 2.4.x, which does not list all of the available Redfish updates on the nodes due to the internal interface not being reachable. This affects only G6/G7/G8 hardware (not supported on G4/G5 hardware).Only certain host versions are available for the Redfish BIOS update in LCM 2.4.x. Ensure the host meets all requirements and is eligible for a Redfish BIOS update. If the system does not meet Redfish requirements, LCM will continue using the legacy(using Phoenix) method to perform the upgrades.There are two scenarios associated with this same issue.Scenario 1LCM inventory page will show "System does not meet Redfish requirements" for one or more nodes:

Log in to LCM leader CVM, to find the LCM leader run the below command from the CVM: 


nutanix@CVM:~$ lcm_leaderLcm leader is at <CVM_IP>

Run the below command from the node that shows the error "System does not meet Redfish requirements":

nutanix@CVM:~$ grep -i 'Max retries exceeded with url:' -B1 ~/data/logs/lcm_ops.out


[2021-02-02 10:36:11.285249] GET - https://169.254.3.254/redfish/v1/odata[2021-02-02 10:36:14.369178] Error while calling https://169.254.3.254/redfish/v1/odata. Details: HTTPSConnectionPool(host='169.254.3.254', port=443): Max retries exceeded with url: /redfish/v1/odata (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f9155d11990>: Failed to establish a new connection: [Errno 113] No route to host',)).


The above logs indicate errors while trying to call internal IP 169.254.3.254.Scenario 2If the BMC/BIOS version is already on the latest version, the LCM inventory page will show "No available updates" for the BIOS Redfish option. Instead, it will show legacy BIOS update options available in LCM for one or more nodes in the cluster:On the node that is not displaying Redfish updates, run the following command : 

nutanix@CVM:~$ grep -i 'Failed to ping the internal IP' -A6 ~/data/logs/lcm_ops.out

[2021-05-03 01:31:12.311761] Generic ping at IP: 169.254.3.254[2021-05-03 01:31:33.355680] cmd: ping -c 1 -W 1 169.254.3.254, out: PING 169.254.3.254 (169.254.3.254) 56(84) bytes of data.

--- 169.254.3.254 ping statistics ---1 packets transmitted, 0 received, 100% packet loss, time 0ms, ret: 1, err:[2021-05-03 01:31:33.355847] Failed to ping 169.254.3.254[2021-05-03 01:31:33.355871] No. of retries left: 0[2021-05-03 01:31:33.355891] Failed to ping the internal IP on AHV, resetting the interface

The above log snippet indicates errors regarding failure to ping the BMC internal IP -169.254.3.254. 
. Save the IPMI configuration file for backup before implementing the workaround. Customers need to save the current configuration because in step-2 IPMI will reset to factory default setting. IPMI will be restored back to the current configuration once the customer performs step 3. 

Note: on ESXi all the ipmitool commands should start with a /. For example:

root@ESXi:~$/ipmitool raw 0x30 0x4a

 

Download the IPMI configuration of the affected node via GUI or from the command line:
	GUI from the IPMI:
		Log in to IPMI Navigate to "Maintenance > IPMI Configuration"
			
			Click on Save which will download the .bin file.
		Command-line from the host:
		root@ESXi:~$/ipmitool raw 0x30 0x4a
		
	Reset the IPMI to factory default from the command line or GUI:
	Reset via GUI from the IPMI:
		Navigate to “Maintenance -> Factory Default” as below, select option "Remove current settings but preserve User configurations" and then click on "Restore":
			
			Click on "Yes":
			
			Wait for at least 2 minutes. IPMI will redirect back to the login page.
		Confirm IPMI is accessible.
	Reset via command line from the host:
	root@ESXi:~$/ipmitool raw 0x30 0x4a
	Reload IPMI configuration from the host if IPMI is not accessible. The IPMI may reboot after restoring the configuration. Wait for 120 seconds in order to let the IPMI complete the initialization.
	root@ESXi:~$/ipmitool raw 0x30 0x4a
	Re-run LCM inventory.

If the above steps don't fix the issue, contact Nutanix Support with the downloaded IPMI configuration file from step 1.. ### 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.