Forum Discussion

PK_Bhatia's avatar
PK_Bhatia
Icon for Nimbostratus rankNimbostratus
Feb 02, 2016

f5 v12 wildcard destination port

Hi,   I tried upgrading the f5 v11.6.0 HF5 to v12.0 but it looks like all the pool with wildcard destination port seems to show up as down, has anyone have any workaround for this issue or if it i...
application delivery
big-ip
LTM
PK_Bhatia's avatar
PK_Bhatia
Icon for Nimbostratus rankNimbostratus
Feb 03, 2016

Nope, that's not the case, at least not with my case. I do have alias port assigned to specific port. Taking an example for my Samba share, I have a virtual server listening to all the ports and so do the pool. But the smb monitor I have is associated with alias service port 445. But right after upgrading to version 12.0.0.0, I got the samba monitor down and service was down as well.

 

And yes, i do understand that I can still use the ICMP monitor but it is not reliable.

 

Thanks for answering and please let me know if something else I can try.

 

awilhelm's avatar
awilhelm
Icon for Employee rankEmployee
Feb 03, 2016
If your pool members or nodes are defined with an FQDN rather than IP addresses, this may be a known issue tracked internally as ID562267. Please open a service request with F5 Support; they can help determine whether this is a correct diagnosis and assist with a workaround.