Forum Discussion
Felkor_29336
Apr 12, 2012Nimbostratus
Syslog & Source IP on cluster
Hello, I encounter a bug with the syslog-ng process : there was no syslog trafic initiated by the F5 on the remote syslog server after a reboot of the BIGIP. This was in fact related to...
Felkor_29336
Apr 16, 2012Nimbostratus
The support give me an other solution, otherwise to perform the upgrade : it is to modify the behaviour of the configuration file of the F5.
(syslog-ng.conf)}
A little procedure here, this could maybe help !
1. Mount the usr partition in rw
mount -o remount,ro /usr
2. Backup and modify the config_base.conf file
Basically, this file determines all attributes of all objects of the configuration, which one are or not sync, etc
cp /usr/share/defaults/config_base.conf /usr/share/defaults/config_base.conf.bak
Locate the following portion of code in the file :
config
class syslog {
category "confpp"
singleton enable
configsyncd enable
fields {
...
include {
display "Include Data"
type string
appdata "unix_config_syslog.replace.include"
clustered enable
configsyncd enable
}
...
}
nested remote_server
Change configsyncd enable to configsyncd disable.
Save the modification.
3. Reload the services in forceload mode
touch /service/mcpd/forceload bigstart restart
After that, when you create a syslog server with a localip, the local ip is hosted in the bigip_base.conf, as in the 10.2.2 versions and above !
Thanks Kevin White from F5 for the tips :)
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects