Forum Discussion
For point 2, In your VS configuration for outbound traffic, make sure to unselect address translation AND port translation from the Virtual settings. This will ensure that when pool member selection occurs, the destination address is not changed to the next hop router IP address. SNAT automap should suffice, although I would recommend using a different address from each link to source from. If you ever need to differentiate that traffic for access controls, having it on a separate IP would be helpful.Also, make sure you limit the default virtual server to only listen on your internal VLANs. There's nothing worse than taking a default deny device, and turning it into a router!
For inbound traffic, the control mechanism is DNS. I would HIGHLY recommend planning this strategy out as follows. You need to delegate a DNS domain to your Link Controller, something like "*.hosting.mycompany.com". The floating IP for each of your links on the LC should be used as the delegated address. UDP port 53 should be opened to the LC floating IP inbound on your ISPs.
Consistent naming is key to being able to track these relationships. Now you want to add your first domain, "www.mycompany.com" Add an DNS entry for www.mycompany.com as a cname pointing to www.hosting.mycompany.com Add virtual servers for www.hosting.mycompany.com for each link. Add a WideIP for www.hosting.mycompany.com which uses the virtual servers which were just created.
This can get interesting if you have more than one hosting facility. You would have to account for them separately such as ".denverhosting.mycompany.com" and ".virginaihosting.mycompany.com". If you have multiple hosting centers, name the appropriately, and they can be referenced with GTM to give you geographical diversity or HA.