Forum Discussion
baldeepbirdy_80
Nimbostratus
NimbostratusF5 Management Pack Issues and Device Discovery
Hi,
Currently experiencing two problems with the F5 MP.
We have deployed the F5 MP to three servers i.e. RMS and two Management Servers. The RMS is showing as green and all healthy but the two MS are showing as warning and critical.
One Management server is reporting the following -
The PerformanceDataSourceConnector connection to Operations Manager Health Service host localhost was lost: Failed to connect to an IPC Port: The system cannot find the file specified.
The second management server is reporting the following -
Data was dropped due to too much outstanding data in rule "CiscoSNMP.Rule.CollectInterfaceOutPctUtil" running for instance "5001" with id:"{009FA890-2584-FFDA-541A-DCD40A7EF969}" in management group "XXXX".
Help with both please.
In addition we are trying to discover two devices. The first went on fine but the second device keeps failing -
Storage Error: 15688314 : [10/28/2009 11:02:13][ManagedDataSourceConnection`3] Connection connect failed: Error=F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host MSERVER could not be established: Failed to connect to an IPC Port: The system cannot find the file specified. : MSERVER
We are now going to completely remove both devices and complete all activites on the RMS.
B
baldeepbirdy_80guys,
we've removed the management pack from the two management servers but they are still listed in f5 management pack monitoring services. How can I remove them from here?
I want to do this before I start from the beginning.
Thanks
Bal- baldeepbirdy_80ok the two servers have cleared out and i only have the rms listed. Now when I try to discover the F5s the system just hangs at the first step of the verification process.
- baldeepbirdy_80guys,
we have managed to get the devices discovered but am getting event log errors as per - http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=62716.
any advice please as this is getting very frustrating. - baldeepbirdy_80ok i got it on and working. I removed one device and the other refreshed and went green. I then added the second device again and that has gone through and is now monitoring.
It looks like if you dont wait for one device to refresh and be monitored it the MP doesnt like it.
Bal - 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
