CIMPROVAGT message in syslog

[Mduffy_1]

I receive the following message every 30 mins in syslog.
syslog: icapd: ERROR: The following low-level error occurred:ERROR: The following low-level WBEM error occurred: GS13600: FAILED TO START CIMPROVAGT "HP_NParProviderModule".


I noticed this happened after I patched one of my vPars to vPar monitor 5.05. Currently I have a nPar with 5 vPars on it. One of the vPars I was patching, and one of the steps was to upgrade to 5.05, after I rebooted the system I have been getting this error message. My other 4 vPars are running vPar Monitory 5.04, they should work together fine, but some reason this error came up, as well as now I can not run vparmodify to add cpu from the systems that have 5.04 on them.
My resolution so far has been just to reboot any of the vPars that are running 5.04, after the reboot the error is gone and I can run vparmodify again. You could also patch it to 5.05 at this time if you would like, but you do not have to.
Does this make sense, this is just from my own observation. I cant boot some of these vPars as they are production servers, and can not handle the downtime. So my question is there another way around this, is my observation correct?

[Steven E. Protter]

Shalom,

Part of the procedure for updaing the vpar software on an npar is to boot all the nodes.

There is no way around this that I know of. I am though pretty new with this, having six weeks of recent full time experience on this.

I did have this very discussion with the responsible admin here and thats what he said.

SEP

[Mduffy_1]

I know this is a small point, but I updated the vPar software on 1 of the vPars, not the others, so I just assumed it wouldnt effect the others. Everything seems to still work fine on these vPars, I guess at this point I am going to have to try to schedule downtime on all of the vPars. This will bring up the problem if I add a vPar to this nPar, and this vPar has a newer version of the vPar software then I am going to have to bring down all the vPars, even though 5.05 should work perfectly fine with 5.04, doesnt that kind of defeat the purpose of adding a system on the fly?