I am curious if there are others out there in my situation. When we have less than 10 users in our test lab pointed a the MWG 7.0.2 it works fine, but as soon as we try a larger group the appliance chokes after less than a day or two. We monitor the processor / memory usage and it does not take a hit, so the hardware and OS do not seem to be taxed, just the MWG application itself. We have attempted four different rollouts since August and the result has been the same where we have had to pull the users off and point them back to the old MWG 6.8 that is in production, since the MWG 7.0 dies. Each problem has been slightly different, supposedly patched by a known issue. We have a pretty straightforward setup as well, with a few groups of users and AD authentication.
We are seriously considering pulling the plug on the upgrade project until MWG 7.1 is released, since we are wasting too much labor on something that should be working. I just feel that we are beta testers at this point.
Anyone else find themselves in this situation?Message was edited by: Tom Cornelius on 1/21/11 9:37:27 AM CST
We are using Policy Based Routing (PBR) to direct users to the proxy. We have two: the production is a MWG 6.8 with 2000+ users and the dev/test is a MWG 7.0.2.
When we want to add more users, we change the PBR for that subnet to point to the MWG 7.0.2 and there are no issues getting the users to the device.
I was just told that this week's failure was being addressed by engineering, since they identified the problem as being within the Trusted Source SDK. A fix is currently in QA and will be available soon.
Same thing happened to me when upgrading my 6.8.6 to 7.0.2. Although I have so many users it failed after 5-10 minutes, support the other day just told me to upgrade to 126.96.36.199 as the fix for this issue is in that release and its related to CPU usage.
Tomorrow during an outage I will be upgrading, I will keep you updated.
I had the same problem and the rev update fixed the problem. CPU load creeps up depending on user load and the appliance crashes. 188.8.131.52.0 has been very stable since.