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

Hi Rob,

 

 

Thank you for the update. I think the way your clustered RMS environment has been set up would have been supported by the F5 Management Pack deployment, while still conforming to Microsoft's best practices regarding RMS workflows, load, etc. Normally, when deploying the F5 MPk in a clustered RMS environment, the RMS cluster nodes should be the first ones targeted for the F5 MPk deployment, and then the other management servers. By default, the F5 Monitoring Service agent is disabled on the clustered RMS nodes. We basically require the RMS deployment for loading the actual F5 management pack, F5 device configuration and related data-sources, etc. The actual monitoring would happen on the management servers, thus complying to MS best practices.

 

 

Coming back to your initial problem, my feeling is that you initially deployed the F5 MPk on a non-clustered RMS, which eventually has become clustered. So initially, our F5 MPk configuration data would be referencing the FQDN of the RMS host. After promoting the RMS to a cluster node, the 'old' deployment of the F5 MPk would stay cluster-agnostic, as it won't automatically adapt to the clustered configuration. By design. If my theory stays true, attempting an in-place upgrade of the F5 MPk from a non-clustered configuration to an RMS-cluster would probably break, as the upgrade would fail to resolve some of the 'old' FQDN references of the [standalone] RMS to the 'new' RMS clustered group resource's FQDN. And this is unfortunately a user case scenario we haven't thoroughly tested yet with the F5 MPk deployment.

 

 

We will investigate this use case and will try to come up with a resolution, but I don't have an ETA for the fix at this time. If you re-deployed on a non-clustered RMS environment, things should pretty much fall into normal, but if you're missing performance data, the first thing to look at would be to check if there are any errors in the F5 Monitoring Log or the Operations Manager event logs. If you have defined your own overrides, make sure they comply with the guidelines described here: http://devcentral.f5.com/wiki/default.aspx/MgmtPack/PerformanceCollectionAndMonitoring.html

 

 

It is very important to have the appropriate targets set up for the collection rule' configuration override (to F5.Object or derived) and the rule property override (to F5.MonitoringService). See the related article for more information.

 

 

If you have problems setting these overrides up, let us know, and we'll further investigate.

 

Julian