RADIUS and route domain

Is this for client VIP or admin GUI/CLI auth? If client auth, I'd say it's a bug--you should be able to specify an auth server in the VIP's routing domain. If it's admin auth, I don't think it would make sense to have all admins authenticated against one routing domain's auth server. For admin, wouldn't it make more sense to define the auth server in the default routing domain?

 

 

Either way, I'd suggest opening a case with F5 Support to check on this. If you do/have already, could you post back what you find? If you get stuck, I can also check with a customer who set up admin auth with a RADIUS server and routing domains.

 

 

Aaron