The performance team noticed that on the DCI MSU Summary report, some LPARs were showing "0" MSUs consumed for a range of 5-minute intervals. At a later time, all LPARs were showing the expected MSU consumption for those intervals. Is this expected behavior with DCI GUI - that reporting might be delayed for some LPARs, but be more current with others?
Release : 2.0
The reported issue is related to some network delays, the controller and agent log need to be checked for TCPIP-related messages.
For example, the agent log will have the below messages