When performing inventory of any of my VMware ESXi nodes (resource type: Operating System) I receive following error/warning message in 'Collect inventory' job log of my Flex System Manager: "ATKSRV630E Managed resource "OS_RESOURCE_NAME_HERE" lost the CIMOM connection. The reported inventory data might be incomplete. Verify the connection between the management server and the managed resource, and verify that CIMOM is running on the managed resource. Next, collect the inventory again.". I have verified the connection between FSM and ESXi node's OS (Actions -> Security -> Verify Connection) and it is OK. FSM accesses the ESXi server's OS using root user credentials and the Access state is OK. I'm running Flex System components on release level 1.3.1.2. What could be the reson of the error message, what are its consequesces and how to fix it?

Concerning your question. You shouldn't need to inventory the OS MEP (managed end point) for ESXi (we get the same message in our lab). An inventory of the Server MEP will give you everything you need. If you want inventory down to your VM level you would discover and manage your vCenter server.

Thank you for quick answer. Yes, it makes much sense, however there is one thing which still worries me, when it comes to inventory. I performed inventory of the server MEP of the same ESXi node and the result is the same as for OS MEP (event ATKSRV630E). See full job log below:

Today I restarted System Management Processors of all nodes with ATKSRV630E inventory error and out of 6 'Server' endpoints with inventory errors - 2 went through the inventory without error after the IMM restart. I have also restarted all the management agents on all ESXi hosts with this problem (using 'services.sh restart' command). To summarize, problem is still not fixed for me and FSM behaviour seems to be 'random'. For sure I will restart everything: ESXi hosts, IMM modules, CMMs and FSM before next PureFlex components update, but even if this works it still doesn't sound like a solution...

Thank you for the detailed information. In short the FSM can be flakey at times and to be complete honest I do not know why it does what it does sometimes. A good thing to try on one of those servers having an issue would be to completely remove it from the FSM and rediscover it. This has cleaned up weird issues in the past. If the issues persist AFTER a removal and rediscovery then I would suggest pulling in IBM support.