Forum Discussion
NimbostratusUse a default route for TMM, but allow remote syslog to work through mgmt interface
Hi,
We have a scenario, where we would like to have a default route in the TMM: Destination: 0.0.0.0/0 Gateway: 10.0.0.1
10.0.0.0/24 is our SNAT egress network. Our management network is 192.168.0.0/24, with default gw 192.168.0.1
This Works, however, when trying to configure remote syslog to server 172.16.0.10, which should be reached via 192.168.0.1, the default route in TMM preceedes the management route, and the BigIP attempts to send syslog messages using out SNAT pool
I cannot quite see why, as we use the built-in syslog-ng facility to push logs to the remote server.
2 Replies
natheCirrocumulus
Erland,
Have you seen the following two docs?
https://support.f5.com/kb/en-us/solutions/public/13000/000/sol13080.html
https://support.f5.com/kb/en-us/solutions/public/13000/200/sol13284.html
So I'd suggest a specific static management route.
Hope this helps,
N
What_Lies_Bene1Cirrostratus
The default management route does not count and the TMM default route takes precedence. Configure a specific management route for 172.16.0.10 (or it's subnet) to point to the default gateway for the management subnet, then it'll work.
