Operational Defect Database
BugZero found this defect 1125 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 976853
SNAT pool traffic-group setting may override non-floating self IP's traffic-group
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP TMOS
Affected releases:
14.1.2.6
14.1.2.7
14.1.2.8
14.1.3
14.1.3.1
14.1.4
14.1.4.1
14.1.4.2
14.1.4.3
14.1.4.4
14.1.4.5
14.1.4.6
Fixed releases:
No fixed releases provided.
Description:
A non-floating self IP fails to respond to ARP on the standby system. ... A standby device does not respond to ARP requests for floating IP addresses. ... If a SNAT is configured on the same IP as a non-floating self-ip on the standby, ARP responses will be disabled for that self-ip. ... Even after deleting the snat, or configuring it for another IP, ARP response for that self-ip will remain disabled. ... The effect of this will be that other IP devices will be unable to communicate with the self-ip after the ARP entry times out. ... For example: -- BIG-IP does not respond to ARP requests for the non-floating self-ip -- ConfigSync no longer working (if the affected self IP is the ConfigSync address) -- Health check traffic fails Note that simply deleting the SNAT translation will not restore service to the self-ip. ... Conditions ... An LTM SNAT translation address has been created which matches a non-floating self IP on the system, and the SNAT is configured in a floating traffic g...
