For redundancy I would recommend you to use the DC1-DC2 tunnel as backup route for your clientsites (depending on how fat this pipe is or can be depending on your wallet and prices in your area). This way if CLIENT1-DC1 link fails but CLIENT1-DC2 still functions then CLIENT1 can still reach servers placed at DC1 (would of course need two metric 2 routes at each CLIENT site which I missed). You could enable QoS in your PAN to make sure that DC1-DC2 traffic is prioritzed over CLIENT-DC1-DC2 traffic. The proxy thingy was just to avoid having public ip's flowing around in your core. If you use a non-transparent proxy then only RFC1918 ip's (assuming you use private ip addresses such as 10., 172. or 192.) will flow through your core and in case one (or many) clients gets infected with a trojan or whatever its somewhat likely that this trojan/badware will try to reach its command and control and if you are lucky an IDS in the core (or the PAN itself) could then scream if it detects ip addresses which shouldnt exist in your network (looking at dstip). The tricky part without loadbalancer is how to use the two DC bluecoats. One workaround is to use PAC (Proxy Auto Config) files which the clients would load in order to find out how to reach Internet, see http://en.wikipedia.org/wiki/Proxy_auto-config for more information. The point of using DC's as gateways to reach Internet is to have fewer licenses, easier configuration (fewer devices to configure regarding url categories etc) but also consolidate logging. If you know that the client sites can only reach Internet through your internet firewalls and proxies at DCs it will be easier to collect these logs and also perform auditing and other operations on the collected logs. Also I assume that you will already have persons for 24/7 standby for the DC's but not necessary for each remote office (client site). But sure if you let each client-site reach Internet directly then they will be more autonomous in case both your DC's fails. Also you could use the content filtering in PAN instead of the BC and just use BC for the proxy stuff (like only allow pure-http and pure-https and such) and let the PAN handle AD-integration (userid), Antivirus, SSL-termination, IDP, URL-categories, AppID etc...
... View more