Forum Discussion
Livius
Cirrus
CirrusHSL not using management interface gateway
Hi all,
I have the following scenario:
HSL configured using a pool which contains a single IP address. That IP is basically a VIP on another F5 which should collect all HSL logging from multiple F5s and send it ac cross to a pool of servers. The VIP has connectivity with all mgmt IP addresses from all F5s.
The problem:
The IP address of "destination" HSL should be routed via management gateway rather than other self IPs gateway. When I try to add that static route via GUI I get the error that the gateway is not connected via an interface. When I try to add the route via CLI it works but traffic still goes via self IP's default gateway.
Any idea?
amintejYou have to add management routes if you want to use management interface for some traffic, only it is possible to configure using the cli, example:
tmsh create /sys management-route lognet network 10.10.10.0/255.255.255.0 gateway 172.16.1.254Check the next article: https://support.f5.com/csp/article/K13284
Stanislas_Piro2Cumulonimbus
This is the LTM normal behavior.
Pool members are only available from TMM interfaces, not Mgmt interface.
As you use Pool, packets are routed only on TMM interfaces and I don't know if there is a workaround.... maybe create a route domain with a VLAN on same network, then create the pool members in this route domain.
PeteWhiteEmployee
What you propose does not sound like a good design - the usual problem with HSL is that it floods the log server with too much traffic. If you are taking logs from multiple devices then you don't want to send it through the management interface anyway - there is a built-in bandwidth limit and it would just cause you issues further down the line.
Create a new self-IP and use that to send to the log servers.