Forum Discussion

Mark_Cloutier's avatar
Mark_Cloutier
Icon for Nimbostratus rankNimbostratus
Sep 24, 2009

Adobe Connect Edge Server problem with 9.4.6

I have an Adobe Connect application with edge servers in the dmz behind a 4.5.10 HA pair of 2400s. I attempted to swap out the 4.5.10 Bigips with a 9.4.6 pair. All other apps worked fine with the 9.4.6 pair, but the Adobe Connect app ran into problems. Basically the edge servers proxy https connections from users into our internal network where another HA pair (9.3.0 pair of 1500s) is load balancing the origin servers (running both the connect web app and the meeting servers) using SSL termination on the BigIPs. The https connections from the dmz, get routed thru the bigip engines via a forwarding virtual server (0.0.0.0:0, all ip protocols). Our internal setup is basically the same design as shown in the Deployment guide on F5's website. These connections would work for 3-5 minutes at which time they would be unable to connect to the virtual server that load balances the connect web app on the origin servers. This resulted in connections backing up on the edge servers at which point those web servers would stop responding. During the time that the Edge servers were unable to connect to the VIP, that VIP was serving internal users directly with no problems. I'm hoping someone else has run into this and can provide some ideas. I have a ticket open with F5, but don't have a resolution yet (Upgrade was done the morning of the 19th, and Adobe app was moved back to the 4.5 engines on Sunday evening the 20th

1 Reply

  • turned out to be that the windows servers were sending traffic out of both of the nics in the teamed nic configuration. That was tolerated by the version 4.5.10 bigip, but the version 9 ltm does a closer inspection, with the Fast L4 profile on the forwarding virtual server and although it passed the syn seq, the syn acks coming back were dropped. Once the teaming nic configuration was changed to only use one nic, everything worked as expected