F5 Management Pack Issues and Device Discovery

Hi Bal,

 

 

I'm sorry to see you're having problems deploying the F5 Management Pack in a distributed management server (DMS) environment. We haven't seen the behavior you're describing and I'm trying to think of possible scenarios that would trigger this problem. I'll run a few tests for a possible repro. On the other hand, in a DMS environment we're recommending to discover devices on the management servers (MS), rather than the RMS. Did you end up discovering the F5 devices on the RMS? I should probably mention that when deploying the F5 Management Pack (F5 MP) in a DMS environment, the RMS installation of the F5 MP will have the F5 Monitoring service disabled, by default. So, if you plan on discovering devices on the RMS, you'll have to enable the F5 Monitoring service.

 

 

That being said (again, assuming that you run everything now on the RMS), still we would recommend going with the SCOM DMS deployment best practices of discovering F5 devices on the MS and we're ready to assist you (we'll do our best to follow up ASAP). If you decide to go this way, we'll need a little bit more information on your environment, for troubleshooting:

 

 

1. Run the system information tool on the RMS and MS hosts (Click here for details). Zip the result files and email them to managementpack(at)f5.com.

 

2. Enable verbose logging support ( for details).

 

 

Also, do you have any overrides defined, targeting the F5 Management Pack?

 

 

Thanks for being part of our community!

 

Julian