For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

RHendle_110546's avatar
RHendle_110546
Icon for Nimbostratus rankNimbostratus
Jun 10, 2010

The requested pool member xxxxx was not found.

Problem description:   We recently upgraded our F5 and then discovered an LTM HA pair of F5's with the SCOM F5 MP.   The discovery was successful and everything "appears" to be working wit...
management
microsoft
scom
Julian_Balog_34's avatar
Julian_Balog_34
Historic F5 Account
Jul 09, 2010
Rob,

 

 

Apparently none of the ports in these unresolved pool members show up in our default port-service name normalization dictionary. And I checked this dictionary also on the latest BIG-IP platform builds. That makes me think that you may have custom entries in your /etc/services file, on your BIG-IP, mapping certain ports to service-names that we don't know of. The /etc/services file keeps the port -> service name mappings. So, if that's the case, we have a problem. Can you please verify your /etc/services file, and can you confirm that you have the following port mappings defined in it (just look for the port number):

 

 

8324, 10672, 8845, 10404, 8070, 14686, etc...?

 

 

If you do have custom mappings for these ports, the immediate workaround to unblock your discovery, would be to remove the custom mappings from the /etc/services file (and these are the mappings for the ports shown in the errors about the requested pool members not found. Would this be a blocker for you? Removing the custom mappings? Are you performing any business / data analysis in your network environment that specifically target those port mappings?

 

 

Let us know, and we'll decide what to do next.

 

Julian