Forum Discussion
Eve_28283
Nimbostratus
May 25, 2010F5 Service Throws Exception - Key Not Found
I have 2 x Managment Servers and for redundancy installed F5 on both and then today I installed the Quest QMX on a single server immeidately after the F5 monitoring service throw and exception - Key ...
Julian_Balog_34
May 28, 2010Historic F5 Account
Evelyn,
Thank you for the information you sent us. I've analyzed the override management pack containing the F5 device related rule overrides and there's nothing wrong with it. I've installed the override pack and tried to get a repro on your problem, and everything went fine. But we were able to reproduce the problem without your override pack and without the presence of the QMX, by creating an instance override for an F5 device related rule. So I'm almost positive the problem is not caused by the QMX.
Now, coming back to your environment and the override pack you sent us, it seems that you possibly have at least one instance rule override targeting an F5 device (or derived) object, set up, somewhere. Apparently this rule override is not saved in the override pack you sent us. It could be in the Default Management Pack or somewhere else (just read through the end to find out how to locate the related override pack). Regardless, you have to find that instance rule override and delete it (and other instance overrides as well, if any, targeting F5 objects), so that you'll make the error condition go away. And for now, you have to stay away from instance rule overrides, or they'll produce the problem you have.
The related fix in our F5 Management Pack code will be rolled out with our next release, very soon.
If you plan on uninstalling the F5 Management Pack and install a newer version, as you mentioned you've tried but got an error, that's most probably because of the overrides and related override pack(s). To find out the override management packs that are depending on the F5 Management Pack, you can right click on the F5 Management Pack in the SCOM Operations Console (Administration section), go to Properties > Dependencies > Management Packs that depend on this Management Pack. This information could also come in handy when trying to locate your instance rule override. In order to uninstall our product, you first need to remove the override management packs depending on the F5 MP.
Let me know if you need further assistance or if you have problems clearing up the error.
Thank you for your patience.
Julian
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects