Forum Discussion
mikeshimkus_111
Mar 04, 2014Historic F5 Account
Hi Steele6599,
Which version of BIG-IP are you running? The AFM module and Secure Web Gateway feature will let you replace TMG completely (AFM is in v11.4, SWG is v11.5).
Publishing external and internal VIPs on different VLANs should be no problem. You'll need to deploy the iApp service twice, once for internal and another for DMZ, and select the VLANs on which each one will listed from within the iApp config.
thanks
Mike
- Steele6599_8766Mar 04, 2014NimbostratusThanks, I was thinking up running the iapp again like you said. Running version 11.5
- Steele6599_8766Mar 13, 2014NimbostratusAll, I have another issue, right now my TMG listens on 192.168.2.150 for both the client access server and Hub transport and then based on the protocol will route to appropriate server farm. How do I go about doing this with the F5? Will I need to re-IP so SMTP comes in on one ip and CAS services come in on another? The new F5's I purchased are running 11.5 version with LTM: GTM-DNS, Rate Limited, LO, BIG-IP (KJJVAWM-IOCJUUW) ◦DNS Rate Fallback, 50 ◦GTM Rate Fallback, 8 ◦DNS Licensed Objects, 0 ◦GTM Rate, 8 ◦DNS Rate Limit, 50 QPS ◦GTM Licensed Objects, 0 •LTM, Base, 2000S (EALUIUO-PZZYAOO) ◦Application Acceleration Manager, Core ◦IPV6 Gateway ◦Rate Shaping ◦Ram Cache ◦Anti-Virus Checks ◦Base Endpoint Security Checks ◦Firewall Checks ◦Network Access ◦Secure Virtual Keyboard ◦APM, Web Application ◦Machine Certificate Checks ◦Protected Workspace ◦Remote Desktop ◦App Tunnel
- mikeshimkus_111Mar 13, 2014Historic F5 AccountYou can create a new virtual server(s) at the same IP address, but listening on the hub tranport port(s). Create a pool for the hub transport servers and make that the default for the new virtual server(s).
- Steele6599_8766Mar 13, 2014NimbostratusThanks, very good point