F5 Service Throws Exception - Key Not Found

We found a possible problem in our F5 Management Pack that may have been exposed by the presence of the Quest Management Xtensions in your SCOM environment. As our fix for this potential issue will be rolled out with our next release of the F5 Management Pack, I’m currently looking into finding a workaround in your particular case, to get you unblocked. For this, I plan on installing and configuring the Quest Management Xtensions on one of our test systems, in our lab, here at F5. Is there anything special that I should be aware of, in configuring the Quest MP, in terms of targeting the monitoring of F5 devices through the Quest MP? I’d like to get as close a match as possible to your environment, to see if we can find a viable workaround to your problem.

 

 

Thank you.

 

Julian