Forum Discussion
Eve_28283
Nimbostratus
NimbostratusF5 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 not found. I am unable to uninstall F5. Trace logs and SEtup Logs attached. Bascially I have disabled the service on 2 server but this is just not exceptable for our requirements.
Does anyone know if F5 can coexist with Quest?
Does anyone know how to resolve the Key Not Found issue?
We are running MP v 1.7 - should we upgrade?
How do i uninstalled Failed F5 applicaton from my second MS?
Any assistance with this is much appreciated. This has been a tough day.
thanks,
Eve
I can't upload files here is the event log entry instead
Unhandled exception in DefaultDomain Detailed Exception Information: F5Networks.F5Exception: Unhandled exception in DefaultDomain ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at F5Networks.ManagementPack.DataAccess.Statistics.StatisticsProcessor`4._AddInstanceRuleOverrides(KeyValuePair`2 ruleSet, Dictionary`2 deviceMonitoringIdToRulesLookup) at F5Networks.ManagementPack.DataAccess.Statistics.StatisticsProcessor`4.GetAllRulesForDevice(IPAddress deviceIP, RuleOverrideCache`2 collectionRuleCache) at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeRulesOnDevice(DeviceDiscoveredEventArgs successContext, Device device) at F5Networks.ManagementPack.Services.DeviceMonitor._CompleteDiscovery(DeviceDiscoveredEventArgs successContext) at F5Networks.ManagementPack.Services.DeviceMonitor._DeviceDiscovered(Object sender, DeviceDiscoveredEventArgs successContext) at F5Networks.ManagementPack.Discovery.DiscoveryManager.OnDeviceDiscovered(DeviceDiscoveredEventArgs discoveredArgs) at F5Networks.ManagementPack.Discovery.DiscoveryManager._OnDiscoveryComplete(Boolean discovered, AsyncDiscoveryInfo asyncInfo, Exception discoveryFailureCause) at F5Networks.ManagementPack.Discovery.DiscoveryManager._AsyncFinishDiscovery(AsyncDiscoveryInfo asyncInfo) at F5Networks.ProgressTracking.Tracer.c__DisplayClass1.b__0() at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure) at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally(VoidVoidDelegate activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure) at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally(VoidVoidDelegate activeCode, VoidVoidDelegate preCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure) at F5Networks.ProgressTracking.Tracer.TraceCall(VoidVoidDelegate activeCode, String action, String area, String category, Int32 id) at F5Networks.ManagementPack.Discovery.DiscoveryManager._DoDiscovery(AsyncDiscoveryInfo asyncInfo) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() --- End of inner exception stack trace ---
- Hi Eve,
We’re looking into your problem and will get back to you as soon as we have a plan / fix / workaround. This will be taken care of with high priority, so please bear with us, and hopefully we’ll get you unblocked.
Thank you for your patience.
Julian Balog
F5 Management Pack Team - 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 - Eve,
Can you also send us the override management pack with the F5 device related rule overrides in SCOM? This will give us more information on the specific overrides that are producing the error condition that you get. My guess is that the problem may not be related to the presence of the Quest Management Xtensions agent on the management server. Instead, you may have some rule [instance] overrides for a specific F5 device - the one discovered on the Management Server producing the problem (and running the Quest Agent) - that are causing the F5 Management Pack collection rule override crawler to fail. You can send us the override pack to: managementpack(at)f5.com.
Thank you.
Julian 
Eve_28283Hi Julian,
Physical Host x64 windows 2008 R2
Quest qmx (latest version) with Cisco and SNMP instrumentation installations
F5 devices are not being managed through Quest.
The above error occurs when both both applications are installed on same Managment Server. 4 cisco switches in quest
Start the quest virtual agents and then F5 Throws the above exception and stops working on the MS
SCOM 2007 R2 CU2
F5 has been installed on another MS and is working
Design calls for redundancy Quest and F5 i.e. both applications must co-exist on both servers.
Is this enough information?
thank you for your assistance,
Eve- Eve_28283Hi Julian I will send the customized override MP for F5 to this email address later today.
thank you. - 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 - Eve,
We have just released a new version of the F5 Management Pack that includes a number of fixes, and overall improves the quality of the F5 MP, we hope.
You can download this release from: http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/54/aft/1174022/aff/2301/afv/topic/showtab/groupforums/Default.aspx
Let us know if this works or if you still run into any issues.
And thank you for your patience through all of this!
Julian
