Fatal Error when upgrade or uninstall upgrade from F5 MP-2.1.1.140 to MP-2.1.3.217

Yes Rob,

 

 

You're right. The only benefit of clustering the F5 Monitoring Service agent on the RMS cluster nodes would be a minimal redundancy support for non-distributed Ops Mgr environments, where there are no other management servers deployed, besides the RMS nodes. And, as you mentioned, in your environment there's no need to cluster the F5 Monitoring Service, since you mostly target the other management servers for monitoring.

 

 

Looking at the error you pointed to, I can see that there are problems with the F5 Monitoring Service trying to connect to the Health Service on host OKCMONTST942. I'd really like to get you unblocked as soon as possible, speed up the troubleshooting time and save you the trouble to gather traces and logs. I think that there might be some mix-up in the F5 MPk configuration data, because of the switch between the clustered and non-clustered RMS environment.

 

 

Let me know if you would be OK for us to set up a remote desktop session (GoToMeeting) with you and try to fix the problems right away. And make it to your best convenience, and I'll accommodate that schedule. Otherwise I can direct you on how to clean-up the deployment of the F5 MP and try to re-deploy again.

 

 

Julian