Forum Discussion
BPetronio_11363
Feb 10, 2010Nimbostratus
Hello tranchungt5, all,
I'm making your example as a case study of a Link Controller configuration, cause i found very similar requesits for my future instalation.
When i was reading your configuration i could understand some mismatch on addressing scheme. I have very few hours of BIGIP, so it could be fault of knowledge by my side. Im sorry if it so.
1. The "203.162.0.1 - - 210.245.0.1" are the ip's of the isp routers u are connecting to ? If im correct, why are you saying u have that same floating ip address ?
2. The links are configured with that router address's, but and the uplink address ? do u left blank ?
3. What are the ip "203.162.0.4 - - 210.245.0.4" corresponding to ? In the scheme i understood it would be the self ip address(floating i guess), but on the configuration list, they are referenced as "Pool_Router" members.
4. In the "inside" u have on the scheme that 172.16.1.1 would be internal ip address(that's what i understood), but u are referencing 172.30.1.3 as Internal Floating IP Address.
5. Regarding VPN connections, there are any tricky issue we must implement on FW, regarding the header manipulation? In fact the vpn is established between ASA and other sites/clients... And ASA will be represented by a Virtual Server with a public IP Address. (Im thinking in NAT Traversal or others)
I would appreciate your comments.
Many Thanks,
Bruno Petrónio