Bug ID 747676: Remote logging needs 'localip' to set source IP properly

Last Modified: Feb 14, 2024

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,, 17.0.0,,, 17.1.0,,,, 17.1.1,

Opened: Oct 23, 2018

Severity: 3-Major


The source ip of log entries sometimes uses the system's self IP address.


Remote log entry has the wrong source IP address.


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.


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 when sending logs to the remote syslog server mysyslogB, enter the following command: modify /sys syslog remote-servers modify { mysyslogB { local-ip }} 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.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips