Operational Defect Database
BugZero found this defect 2032 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 747676
Remote logging needs 'localip' to set source IP properly
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP TMOS
Affected releases:
13.1.0
13.1.0.1
13.1.0.2
13.1.0.3
13.1.0.4
13.1.0.5
13.1.0.6
13.1.0.7
13.1.0.8
13.1.1
13.1.1.2
13.1.1.3
Fixed releases:
No fixed releases provided.
Description:
Severity: 3-Major ... Symptoms ... The source ip of log entries sometimes uses the system's self IP address. ... Impact ... Remote log entry has the wrong source IP address. ... Conditions ... This occurs during system start-up if syslog-ng starts before the management IP and route are up. ... This issue can also occur in a high availability (HA) environment. ... Workaround ... Use tmsh to set the local-ip parameter as per: https://support.f5.com/csp/article/K13080#localip For example, to configure the BIG-IP syslog to bind to 10.10.10.10 when sending logs to the remote syslog server mysyslogB, enter the following command: modify /sys syslog remote-servers modify { mysyslogB { local-ip 10.10.10.10 }} Note: For BIG-IP systems in a HA configuration, the non-floating self IP address is recommended if using a TMM-based IP address. ... Note: In case a nonexistent localip is configured in include option, configure a unique persist-name per https://cdn.f5.com/product/bugtracker/ID740589.html.
