Can we use management IP address to get ASM signature update ? We have F5 BIG-IP LTM & ASM in inline mode. we have default route pointing to FW DMZ interface IP address. When I am trying to update signature I can see on firewall that F5 is using external interface selp IP to connect with F5 signature update sites. Is there anyway to use management ip instead external interface selp ip address.
Note: The BIG-IP ASM system consults Traffic Management Microkernel (TMM) and Linux routing tables when requesting attack signature updates using the Automatic Method. The source IP address of the resulting traffic uses either a non-floating self IP address or the management IP address, depending on the matching route.
So, yes looks like it’s possible. You’ll probably need to do a more specific route to use the mgmt int.
Moreover, is it possible to use same management ip address to communicate with syslog server & smtp for email notification. I added the route for syslog server by using same command but firewall is showing external selp ip while bigip is communicating with syslog server.
to be honest i find it odd that the F5 would first try the default route (non management) before trying management. i have a setup where ASM pulls it via the mgmt interface without a specific route for it. that would be quite annoying as the IP can change.
We are using https proxy to connect to the F5 cloud and we like to use the management interface for signature update and syslog, in this case will the below command is still applicable: create management-route $ip/32 gateway $mgmt-gateway-ip