### Human: Can you tell about LCM Log Collection Utility. ### Assistant: Overview and instructions on using LCM Log Collection Utility..  PurposeLCM (Life Cycle Manager) Log Collection Utility provides an independent script designed to collect all the important log files necessary to debug any LCM issue.

NCC log_collector bundle is significant in size and contains multiple files that are irrelevant to LCM. In contrast, Log Collection Utility collects only the files that are relevant to LCM workflow thereby reducing the log bundle size and speeding up the process of log collection.The utility is available in LCM version 2.2 or later by default. It could also be used on earlier versions of LCM.Functionality

Collects LCM log files.Detects if the node is stuck in Phoenix and collects kernel logs.Collects logs for the services with which LCM interacts (Example: Foundation, Prism, etc.).The utility state is independent of such of the LCM hence it is capable of collecting logs even if the framework is down.Parses LCM configurations from Zookeeper nodes.

CaveatsThe script cannot pull logs from the node booted into Phoenix when the node's IP address is not reachable over the network. In that case, apply the respective CVM (Controller VM) IP address to the Phoenix instance using IPMI following KB 5346 before running the script. Once the network is restored, /tmp/phoenix.log should also be collected from phoenix for troubleshooting purposes.Files and information collected

Node level information
	LCM leader
	Logs from CVM
	LCM leader
	Command output from Phoenix
	LCM leader
	. For LCM 2.3.1 or later (automatic log collection)

LCM 2.3.1 automatically triggers the LCM log collector utility when any LCM operation fails.Log bundle will be created in /home/nutanix/data/log_collector/.For LCM 2.3.1.1 and later, LCM prints Log location along with the failure message as below. Log into the CVM IP to fetch the LCM log bundle and upload it to the Support case for review.

Operation failed. Reason: LCM operation kLcmUpdateOperation failed on phoenix, ip: [xx.xx.x.xx] due to Multistage upgrade encountered an error: ('The read operation timed out',). 

For LCM 2.2.x or later (manual log collection)

It can be used to trigger a new log collection.Run the following command from a CVM to begin log collection.

Operation failed. Reason: LCM operation kLcmUpdateOperation failed on phoenix, ip: [xx.xx.x.xx] due to Multistage upgrade encountered an error: ('The read operation timed out',). 

Sometimes you might  see below error message :

Operation failed. Reason: LCM operation kLcmUpdateOperation failed on phoenix, ip: [xx.xx.x.xx] due to Multistage upgrade encountered an error: ('The read operation timed out',). 

If you get the above error, please look for the file python lcm_log_collector.pyc instead and run the command shown below:

	Operation failed. Reason: LCM operation kLcmUpdateOperation failed on phoenix, ip: [xx.xx.x.xx] due to Multistage upgrade encountered an error: ('The read operation timed out',). 
	

Log bundle will be created in /home/nutanix directory on the node from which the script is executed, with the name in the following format:

Operation failed. Reason: LCM operation kLcmUpdateOperation failed on phoenix, ip: [xx.xx.x.xx] due to Multistage upgrade encountered an error: ('The read operation timed out',). 

For LCM 2.2.x, log bundle will be created in /home/nutanix/data/logs/lcm_logs/.

For LCM 2.3 and later, the log bundle will be created in /home/nutanix/data/log_collector/. 

For Uploading the logsOnce the logs are collected refer to KB-1294 for different methods to upload the LCM logs to 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.