Forum Discussion
Jeremy_Bridges_
Nimbostratus
NimbostratusSCOM 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 actually on the F5. See the first attachment for what we see in SCOM, and the second attachment for what we see on the F5 management site.
Here are the steps we did with this pool that led to this final state:
1. Created pool with 10.41.53.53 and 10.41.53.147 as pool members.
2. Restart of the 10.41.53.147 server caused the IP to be changed to 10.41.53.200.
3. Created new pool member with IP of 10.41.53.200 and removed the old pool member that had an IP of 10.41.53.147.
How do we get rid of the old 10.41.53.147 pool member in SCOM?
- 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.
Jeremy_Bridges_Adding and then deleting the old 10.41.53.147 pool member fixed the issue. Thanks!
