Forum Discussion
Jeremy_Bridges_
Nimbostratus
NimbostratusSCOM 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...
Jeremy_Bridges_Nimbostratus
NimbostratusNot to complicate the matter, but I have found an additional problem. If pool members are changed on a pool member, it seems to stop reporting its status correctly. Here is how I discovered this issue:
At the time of the re-discovery, a pool by the name of GinnyE-DEV had three pool members:
10.41.53.216:80 (Up, Disabled)
10.41.54.82:80 (Up, Enabled)
10.41.54.83:80 (Up, Enabled)
Later, I removed the first node and added a different node:
10.41.53.92:80 (Up, Enabled)
10.41.54.82:80 (Up, Enabled)
10.41.54.83:80 (Up, Enabled)
For some other testing, I shut down the web service on the first two of these machines. So, it looked like this:
10.41.53.92:80 (Down, Enabled)
10.41.54.82:80 (Down, Enabled)
10.41.54.83:80 (Up, Enabled)
However, after all of this, the SCOM status still represented the first state of the pool members. See the attachments for the final state of the F5 and SCOM.
