Installation of F5 Management Pack Fails

Hi John,

 

 

Can you run the diagnostic script on the troubleshooting page and reply with the results. Specific information that will likely help us:

 

- version of the F5 Management Pack

 

- assemblies installed related to Operations Manager and F5

 

- event log errors

 

 

Can you also look in the F5 Monitoring event log, and Operations Manager event log for any errors? In the Operations Manager event log, you can look for errors related to loading the F5 Data Source.

 

 

Thanks,

 

Stephen

 

F5 Management Pack

Hi,

 

 

Thanks for the technical info ~ that looked very helpful.

 

 

This error is likely the culprit:

 

ThresholdRuleOverrideMonitor encountered an unhandled exception: Terminal=True Error=F5Networks.ManagementPack.DataAccess.ManagedConnections.OperationFailedException: Crawler RuleOverrideCrawler`2 was not successfully initialized: Operations Manager authentication failed: ls1opsmgr.LS1.LOCAL User: LS1\ls1_opsadmin ---> F5Networks.ManagementPack.DataAccess.DataConfigurationException: Operations Manager authentication failed: ls1opsmgr.LS1.LOCAL User: LS1\ls1_opsadmin ---> Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException: The user LS1\ls1_opsadmin does not have sufficient permission to perform the operation.

 

at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)

 

 

The F5 monitoring service is running as ls1_opsadmin in your setup, and it is attempting to access the the Opsmgr SDK to review monitoring rules and overrides, but failing with a permission error.

 

 

Can you verify your account LS1\ls1_opsadmin has SDK access to Opsmgr? You can verify this by logging in as that account, and then opening either the Opsmgr PowerShell Console, or the UI Console.

 

 

Thanks,

 

Stephen

Hi,

 

 

When I logged in as that user and loaded the Ops Console, it prompted for credentials. So I added that user to the SCOPS Admin group and logged back on and fired up the console - straight in. However having done that I thought I'd be able to restart the F5 Monitoring service, this failed.

 

 

Do I need to do anything else?

 

 

John

Hi John,

 

 

Essentially, since the data source was not loaded [due to the auth error], and the Health Service indefinitely disabled the F5 Data Source, without restarting the Health Service, the F5 monitoring service can not connect to the F5 data source, and will fail to start. There are likely related errors in your event log.

 

 

I would suggest a few things:

 

 

1) Open the Services administrator tool and verify the credentials for the F5 monitoring service are provided and saved, to ensure it can start

 

2) Verify the Health Service is running as your custom admin account, the credentials are stored [in the Services tool], and the service is running

 

3) Restart the [Scom] Health Service ("Restart" in Services tool)

 

- when a data source module fails in the Health Service, the Health Service will disable that data source [in this case, the F5 data source]. Restarting the Health Service is the recommended solution

 

4) After restarting the "Health Service" you should see it start. Then recheck the Operations manager and F5 event log, to verify that the authorization failure did not occur again.

 

5) Restart the F5 monitoring service [via the Services tool will work]

 

 

Let us know if that works for you.

 

 

Thanks,

 

Stephen

 

F5 Management Pack

Hi,

 

 

Unfortunately I am still unable to start the F5 monitoring service, it simply comes back with a timeout message. Looking in the Application Event Log, I've found these events:

 

 

Event Type:Error

 

Event Source:.NET Runtime 2.0 Error Reporting

 

Event Category:None

 

Event ID:5000

 

Date:24/08/2009

 

Time:12:54:11

 

User:N/A

 

Computer:LS1OPSMGR

 

Description:

 

EventType clr20r3, P1 f5mpsvc.exe, P2 1.2.0.0, P3 4a5bc0f0, P4 mscorlib, P5 2.0.0.0, P6 492b834a, P7 343f, P8 15a, P9 system.unauthorizedaccess, P10 NIL.

 

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Data:

 

0000: 63 00 6c 00 72 00 32 00 c.l.r.2.

 

0008: 30 00 72 00 33 00 2c 00 0.r.3.,.

 

0010: 20 00 66 00 35 00 6d 00 .f.5.m.

 

0018: 70 00 73 00 76 00 63 00 p.s.v.c.

 

0020: 2e 00 65 00 78 00 65 00 ..e.x.e.

 

0028: 2c 00 20 00 31 00 2e 00 ,. .1...

 

0030: 32 00 2e 00 30 00 2e 00 2...0...

 

0038: 30 00 2c 00 20 00 34 00 0.,. .4.

 

0040: 61 00 35 00 62 00 63 00 a.5.b.c.

 

0048: 30 00 66 00 30 00 2c 00 0.f.0.,.

 

0050: 20 00 6d 00 73 00 63 00 .m.s.c.

 

0058: 6f 00 72 00 6c 00 69 00 o.r.l.i.

 

0060: 62 00 2c 00 20 00 32 00 b.,. .2.

 

0068: 2e 00 30 00 2e 00 30 00 ..0...0.

 

0070: 2e 00 30 00 2c 00 20 00 ..0.,. .

 

0078: 34 00 39 00 32 00 62 00 4.9.2.b.

 

0080: 38 00 33 00 34 00 61 00 8.3.4.a.

 

0088: 2c 00 20 00 33 00 34 00 ,. .3.4.

 

0090: 33 00 66 00 2c 00 20 00 3.f.,. .

 

0098: 31 00 35 00 61 00 2c 00 1.5.a.,.

 

00a0: 20 00 73 00 79 00 73 00 .s.y.s.

 

00a8: 74 00 65 00 6d 00 2e 00 t.e.m...

 

00b0: 75 00 6e 00 61 00 75 00 u.n.a.u.

 

00b8: 74 00 68 00 6f 00 72 00 t.h.o.r.

 

00c0: 69 00 7a 00 65 00 64 00 i.z.e.d.

 

00c8: 61 00 63 00 63 00 65 00 a.c.c.e.

 

00d0: 73 00 73 00 20 00 4e 00 s.s. .N.

 

00d8: 49 00 4c 00 0d 00 0a 00 I.L.....

 

 

Please help.

 

 

John

Hi John,

 

 

The "unauthorized access" error you're hitting while trying to start the F5 Monitoring Service may be the result of the service account (LS1\ls1_opsadmin) having restricted NTFS, registry or other system resource access. The event log doesn't give us the details. For troubleshooting I would assume the LS1\ls1_opsadmin account has local admin privileges on the box (or at least read-write access to the F5 Management Pack installation folder: %Program Files%/F5 Networks/Management Pack/).

 

 

And to find out more, I would suggest attaching the trace log capturing the service start-up. Please do the following:

 

 

- enable the verbosed logging - see the "Verbose Logging Support" section in the Troubleshooting page (Click here).

 

- attempt to start the F5 Monitoring Service (using the Services Control Manager), wait for the error.

 

- zip the trace.log file located at %Program Files%/F5 Networks/Management Pack/log and post it here (if the service account doesn't have the privileges I was mentioning above, it may not even be able to write into the trace log file).

 

 

We'll take the trace log and analyze it thoroughly and hopefully we can help.

 

 

Thank you.

 

Julian

 

F5 Management Pack

Hi,

 

 

I've now managed to get the service started, it was down to permissions. Basically the service account for the F5 MP did not have any rights on the SCOM server.

 

 

I have another issue relating to discover, shall I start a new post for this?

 

 

John

Thanks for the update, John.

 

 

We'll look at improvements to the product to help identify these permissions issues in a more transparent way.

 

 

Yes, if you wouldn't mind creating a new post for the discovery issue, we'll be glad to help. Each post thread is tracked separately in our support system, so it helps to separate resolved issues from active issues.

 

 

Thanks

 

Stephen (F5)