Hoping somebody can help me understand what I'm doing wrong here. Here is the diagram:
[![enter image description here][1]][1]
We have an ASA sitting at the edge. The FirePower module is connected via the management interface (with "no ip address" configured on ASA, but IP configured on FirePower). The ASA is managed through interface 1/2.
There is an exit subnet configured that should be used for routing all traffic to/from the outside.
The environment has a separate subnet for management (physical devices mostly, hyper-v, storage, etc) which is the 10.10.5.0/24 network and another subnet for end-user-accessed servers, pretty much all VMs. The ASA has to contact some of these servers for various network services like DNS, RADIUS, and others. So if I want the ASA to authenticate a VPN user through RADIUS, I would like it to send that traffic via 10.10.5.1, not 172.16.98.1. I can't get this to work. I believe the routing is breaking. I've been reading about management-only routes, but I can't seem to wrap my head around what I'm doing wrong here. The TAC engineer is very intelligent, but uninterested in going beyond break/fix. Is this is architecture design flaw?
Much appreciated.