Use diagnostic interface to route to ISE for Radius

[Dan Eyster]

I have a customer that needs to use the diagnostic interface to reach their ISE server for VPN radius auth.  He added a route to the diagnostic interface in FMC and can ping it from the CLI.  However, when he tests the VPN connection, the syslog messages show that the ISE/Radius server cannot be reach.  We also configured the radius server group to use the interface to reach the ISE server.  Leaving it blank sets FMC/FTD to use the diagnostic interface to connect.

TIA,

Dan

[Francesco Molino]

Hi

When you configure a radius server you have 2 choices: routing or interface.
When you choose interface and you select your diagnostic, do you see any logs on your ise or did you run a tcpdump to see if packets are coming in?
Why you want to use the diagnostic interface which is not recommended to be configured by Cisco?
Can you share your config regarding radius?