Last Modified: Jul 15, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Fixed In:
2.1.0
Opened: Mar 26, 2025 Severity: 3-Major
Existing Virtual Server (VS) is deleted and recreated during the gateway CR update, even when the update operation results in existing virtual server to be valid.
Traffic meant to existing IP's virtual server is impacted
1. The cluster is configured as dual stack with dual stack config in Vlan and BNKGateway CR. 2. The Gateway CR references a BNKGateway. 3. Initially, the user specifies an IP address (either IPv4 or IPv6) in the Gateway CR. Let’s say IPv4 for example. 4. The user subsequently updates the Gateway CR to include an IPv6 address as well. As a result, the existing Virtual Server (VS) is deleted and recreated during the Gateway CR update, even when the update operation results in existing virtual server to be valid. The virtual server corresponding to v4 address in the example specified is deleted and recreated.
There are 2 workarounds to this issue: Workaround 1: When Gateway is configured with Static IP (user provided IP), BNKGateway section should not be added. Workaround 2: When Gateway is configured with Static IP (user provided IP) and is pointing to BNKGateway with Dual Stack, configure both IPV4 and IPV6 as Static IP.
Fixed an issue causing the virtual server to be recreated during an update.