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

RPriesing_79448's avatar
RPriesing_79448
Icon for Nimbostratus rankNimbostratus
Nov 18, 2009

Event ID 301 in F5 Monitoring Log on OpsMgr Server

Not sure if these are related to my previous posts. Getting Event ID 300 and 301 on a regular basis. 300 states connection established with F5 node. 301 states:     Failed to discover d...
management
microsoft
scom
RPriesing_79448's avatar
RPriesing_79448
Icon for Nimbostratus rankNimbostratus
Nov 18, 2009
Looks like this and the BIG3D restarting are related. They both start when I enable monitoring. Discovery appears to work as i am able to run the config reports without issues and see the corect configs/pool/nodes etc.....