Exchange 2010 load balanced via BIG-IP
Hello guys, Currently we have our Exchange (2x CAS servers) configured via BIG-IP. The Exchange VLAN is stretched up to F5 so VS and 4x CAS servers sits within the same VLAN/Subnet which works fine. I'm working on migration to a new/separate BIG-IP appliance and was wondering what is the downside/disadvantage of having exchange VS in a different VLAN/Subnet? I know there is an option to get this configured on F5 via iApp ("Same subnet for BIG-IP virtual servers and Client Access Servers" or "Different subnet for BIG-IP virtual servers and Client Access Servers") but not too sure if everything will work as works right now. The CAS servers default gateway is pointed to the VLAN interface configured on our main router (NOT VS sitting on F5) and would like to keep it that way. I'm asking as I have recently been told the DNS for autodiscovery.domainname.co.uk has to be pointed to the IP address which lives in the same VLAN/subnet as the IP addresses of CASes otherwise DAG will not work... Has anyone tried that? I would much prefer to have only 2x VLAN configured on F5 appliances (Internal VLAN & External VLAN) rather than 3x.Problem with exchange_2010_2013_cas.v1.5.1 iApp
Hi guys, I'm currently working on migration of BIG-IP 3900 to a brand new vCMP hosted on BIG-IP 7250. On the old (BIG-IP 3900) we have iApp exchange_2010_2013_cas.v1.4.0 deployed which works perfectly fine. I would like to deploy a newer version of the same iApp on the new box (BIG-IP 7250). New Virtual Server will have an IP address from the same subnet/vlan as the old one and will be pointed to the same CAS - pool members. I will be using different self IPs etc. Both F5 appliances share the same VLANs (Internal, External and Exchange) but all IPs are different - no IP conflicts. The question which I have is - can the deployment of the new iApp on the new BIG-IP affect somehow the current setup without changing DNSes and autodiscovery IP addresses?
Discrepancy: Current Virtual Server Connections
I've noticed a discrepancy between the way the F5 cluster and Exchange measures CAS connections. When checking the number of current connections in the F5 virtual server stats for Exchange OWA (HTTP/HTTPS), I was very surprised to see that the number of connections was far higher (as much as 5 times higher!) than the number being reported by Exchange. I was wondering if this is due to a difference in how "connections" are counted. If so, how are connections counted by the F5 virtual server stats?