Floating self IP and virtual IP using same address.

By chance, did you try netcat? You may find that curl, wget or netcat will honor the route domain syntax - I'm not sure though.

 

 

You basically need utilities that support IPv6 to connect from the LTM CLI to non-default route domains. So curl and netcat on LTM will work. But wget isn't included by default.

 

 

Aaron - if you're doing an HTTPS VIP, you're no longer able to manage device via Self-IP:443 then? How about if you're doing SNAT Automap? Do replies to automap address hit VIP instead of self-ip?

 

 

I expect if you define a VS on 443 on an IP defined as a self IP, you won't be able to connect to the admin GUI on that IP. If you enable SNAT using that self IP, TMM shouldn't use any reserved ports (<1024) to source traffic from. The TMM connection table should handle packets for established connections so there shouldn't be an issue there.

 

 

Aaron