1 of 1 people found this helpful
if you have two preloaded KMs kindly place merge command so the updated policy could not replace the old PreloadKM.
Thanks Amit, I couldnt find any policy with merge operation. Can you suggest how it can be done.
Do you have PCM for patrol.
Yes Amit I do have the PCM but I had the idea that CMA should be sufficient and we wouldn’t need PCM :-)
Do you think it’s due to any other configuration . At Patrol agent or at CMA .
I would also want to understand the issue before putting in the workaround .
I have use PCM instead of CMA cant say much about CMA.
Now, how to replace Delete with Merge:-
In pcm 1. Take locate latest backup of configuration.
2.copy both Preloaded km
3. in Place of "delete" place Merge
4. Push the KM in to patrol agent and reinitialize the service.
Regarding the issue occurrence is this happening in all of your patrol agent or some specific once.
when configuring agents through CMA it's perfectly normal to have a preloadedkm under ConfigData with the KMs coming from the policy and the old preloaded variable under AgentSetup empty. This shouldn't be a problem. My agents are configured this way as all monitors must come and be configured by CMA, no mix with PCM allowed !!
Besides you shouldn't tamper with ConfigData variables with PCM as they would get overwritten every time the policy is applied.
In my opinion the problem here is different. If the KM solution does not run, i'd check if it's installed and if it's a version compatible with the OS where its installed. Besides, what does the PA log says ? Is the KM solution being loaded at all ?