Forum Discussion

CEnroth's avatar
CEnroth
Icon for Nimbostratus rankNimbostratus
Oct 28, 2023
Solved

LTM Policy don't send to external log server

Hi Can someone explain to me, what im doing wrong. I have a policy attached to a Virtual-Server, and it is triggered when a specific URI enters. There are two actions, one that logs a message to l...
devops
  • Paulius's avatar
    Paulius
    Oct 28, 2023

    CEnroth This might be one of those instances where you try the iRule equivalent and see if it has the same results. If you do have the same result you might have to reach out to F5 TAC to see if it's an unkown bug or possibly a missconfiguration.

Paulius's avatar
Paulius
Icon for MVP rankMVP
Oct 28, 2023

CEnroth The management interface isn't automatically used for syslog and would be completely dependent on your routing table for your management interface along with the routing table for traffic that the F5 load balances and/or forwards. You can verify what's being used by running the following two commands.

list sys management-route one-line
list net route one-line

The first command will show your statis routes that you have configured for the management interface and the second will be the routes for your general load balanced and/or forwarded traffic on the F5. Please note that the default route on the management interface does not supercede the default route on the routed interfaces of the F5 and the only thing that would supercede it is a specific route on the management interface or if the subnet is directly connected on the management interface. If your F5 is in path it will use whichever interface is closest to the routed destination to communicate with the log server.