Forum Discussion
Jeremy_Bridges_
Nimbostratus
16 years agoSCOM 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 ...
Dave_Ruddell_79
16 years agoHistoric F5 Account
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.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects