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
NimbostratusThat is correct, we have just RMS servers.
As for the pool member's status, I don't have a "Refresh Health" task (see attached screenshot). Did you mean the refresh button when you talk about the "Refresh Health task"? If so, it won't show the correct status no matter how many times I click it.
Maybe you meant the Recalculate Health or Reset Health buttons on Health Explorer?
The state change events you mention seem to be the correct times. But, they don't entirely agree with the events I see in Health Explorer for that pool member (see second attached screenshot).
The F5 must have sent out the notification that this pool member was down. Our QA SCOM server has the correct status for the pool member (see third screenshot).
Can you tell me more about these notifications that you speak of? What protocol do they use? Can they only be sent to one recipient, or can they be sent to multiple monitoring applications?