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
Aug 19, 2009

SCOM and Pool Member Discovery

We have run across a management pack issue that will cause some confusion in monitoring our applications using SCOM and the F5. Essentially, the discovered pool members of a pool don't match what is ...
management
microsoft
scom
Dave_Ruddell_79's avatar
Dave_Ruddell_79
Historic F5 Account
Aug 19, 2009
You can rediscover the BigIP, which will refresh all entity data inside SCOM, but the simplest workaround for now would be to create the 10.41.53.147 poolmember on the bigIP again... wait for SCOM to show it as YELLOW, then delete it from the BigIP again and our service will receive a configuration update saying the object was deleted. I'm not sure why it hung around, but we'll replicate the scenario and see if there is anything we can do on our end.