The requested pool member xxxxx was not found.

Rob,

 

 

From your latest post, where you mention that the virtual server port shows up in SCOM as PXC-ROID (e.g. UDP:4004), I can see that there might be a problem in our F5 Management Pack with correctly interpreting ('normalizing') this port. And for this matter we cannot correctly resolve the virtual server hierarchy in the SCOM health model, and then your underlying pool members end up not being monitored. That's at least my first guess to your problem, but I'll try to get a repro in our LAB and hopefully I'll be able to tell more. In the meantime, if you can send us the exact configuration of your virtual server as it is shown on the F5 device (not in SCOM), this will help us in trying to address the problem. In particular, we're interested in the name/port values defined on your virtual server and underlying pool members. Probably the best would be to run a qkview and send us the results. You can send this information to managementpack(at)f5(dot)com.

 

 

Thank you for your patience.

 

Julian