APM in a different route domain

Hello all,

 

I'm hoping someone might have had this situation before and might be able to point me in the right direction.

 

Current setup:

 

BIG-IP with LTM and APM 2 different route domains

 

Previously everything we have created within the F5 environment has been in the default route domain 0 and all portals created here have worked fine (RDP, web links etc). Recently we have re-designed the edge of our network and now routes in and out of the F5 via route domain 1.

 

I have now created 2 new elements - a new user partition with a default route domain of 1 and a new APM portal page / LTM virtual server in the new partition.

 

In the new portal (in route domain 1) I can login fine with Active Directory authentication and I can see any resources I create within the webtop. My issue is that I am not able to RDP any server I present on this new portal.

 

From within the SSH shell, I can set my route domain to 1 using the rdsh 1 command and then I am able to successfully connect on port 3389 to the server in question, which I believe tells me that the path is routable. The part I'm unable to work out is why it won't work when trying to SSL-VPN through an APM portal in a different route domain.

 

Has anyone else tried to do something similar to this before with APM portals in a different route domain?