Bug ID 479872: Corresponding protocol profiles must exist on both clientside/serverside

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10

Opened: Sep 17, 2014

Severity: 3-Major

Related Article: K16284

Symptoms

Virtual servers configured without protocol profiles on both the clientside and serverside do not pass traffic.

Impact

Attempts to connect to the virtual server might result in RSTs ('no local listener'), or the virtual address might not respond to ARP if there are no other functional virtual servers on the same virtual address. Virtual servers affected by this issue do not pass traffic.

Conditions

This occurs on virtual servers configured without protocol profiles on both the clientside and serverside.

Workaround

If a protocol profile with a context (clientside or serverside) is specified when defining a virtual server, ensure that a protocol profile is specified for the peer context.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips