Bug ID 646491: GTM autodiscovery shows same status for tcp+udp virtuals using the same dest:port

Last Modified: Feb 28, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP GTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 14.0.0,,,,

Opened: Feb 18, 2017
Severity: 3-Major


With GTM autodiscovery, when virtuals having same dest:port but different protocols from same ltm target, these virtuals have same status(both down or both up).


If you have two virtuals configured with the same IP:port, and you use those virtuals in gtm pools, you could have a virtual server down, and yet gtm would see it as still being up (or up, and seen as down), and there are no warnings, no messages to let them know anything is wrong.


Virtual servers have same dest:port but different protocol from the same ltm target and GTM enables auto discovery.


Manually define the ltm-names, allowing gtmd to pass unambiguous requests to mcpd over iquery like this: modify gtm server gtm_myself virtual-servers modify { /Common/vs1_tcp { ltm-name vs1_tcp }} modify gtm server gtm_myself virtual-servers modify { /Common/vs1_udp { ltm-name vs1_udp }}

Fix Information


Behavior Change