Tested this and the robots have only cpu total.
mcs deployment doesn't play nice when either IM or AC is also used to make any config change so that might be one possible cause.
Could pick a test server to add to the group that doesn't have cdm and then make a minor change to the profile such as change the log level which will force a redeployment.
Then see what happens with that test server.
------------------------------
Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 01-25-2021 03:54 AM
From: Asi Aker
Subject: MCS CPU profile doesn't deploy correctly
Hi,
I have created a policy to collect the QOS of the total cpu metrics.
I have checked all robots and it seems like the configuration is always deployed with all cpu metric collection enabled for both total and individual cpu.
Does any one managed to figure that out?
I have installed all outstanding hotfixes up to 20.3.2HF2 for MCS
Thanks