For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jeremy_Bridges_'s avatar
Jeremy_Bridges_
Icon for Nimbostratus rankNimbostratus
Dec 05, 2009

SCOM F5 Objects Not Consistent with Objects on F5

We have been working with the F5 management pack for a while in our DEV environment and have just set it up in QA. In both environments, we have noticed that the objects that are discovered in SCOM a...
management
microsoft
scom
Jeremy_Bridges_'s avatar
Jeremy_Bridges_
Icon for Nimbostratus rankNimbostratus
Dec 10, 2009
I don't see any more errors like that in the event log since I performed the re-discover at 5:30 PM on 12-7 (see attached screenshot). The error I have seen since then was the iQuery error mentioned above.

 

 

As for the rest of the information messages seen in the attached screenshot, they are of two varieties: event ID 100 and 300. These are pictured in the other two attached screenshots.

 

 

As far as trace logs go, I restarted the F5 monitoring service and sent the logs I found in the "C:\Program Files\F5 Networks\Management Pack\log" directory. Last couple times, I have sent just the trace.log file found at the location above. Since you haven't been able to find what you need in there, I decided to send everything in the directory. Let me know if you need the setup.log file too.