EV 9.02 Event id 3419

[holcomb76]

saw this thread with no resolution. anybody come up with a fix.

https://www-secure.symantec.com/connect/forums/event-3419-and-2217-ev9-exchange-2010

i have this same issue and can get around it by bypassing the F5 load balancer and pointing my EV journal server directly to the cas server.....

[AndrewB]

have you seen this? http://www.symantec.com/docs/TECH145331

if you're able to resolve the issue by bypassing the F5 then i think you've resolved it on your own since this doesn't appear to be an issue with EV itself.

here are a couple more short articles that might be of interest:

http://www.symantec.com/docs/TECH146340

http://www.symantec.com/docs/TECH169970 (this one actually says to do what you're doing with bypassing to resolve the issue)

[AKL]

Just wondering or trying to understand the concern - I see you wrote that "can get around it" by bypassing F5 load balancer.

Do you want resolution where you can use load balancer?

[JesusWept3]

another question, do you use Blackberry Enterprise Services at all?
If so, odds are very high your BES Admins have seen this as well, may be worth checking with them to see if they've seen it and how they dealt with it

[AndrewB]

true. BES and GOOD both typically need to bypass F5's as well. the Blackberry article is referenced at the bottom of the 3rd technote i posted.

[JesusWept3]

ah yeah, didnt read the links , sorry :)
theres the answer then!

[AKL · Accepted solution]

Just wanted to update for all that admins (EV/BES/Good) can use F5 load balancer to connect to CAS Array after updating a setting on load balancer itself.

• iRule: exchange-snpool-persist
• Idle Timeout: 7200 seconds

Once above setting are in place, there shouldn't be any issue seen. There is no formal technote from Symantec on this, but below is note from RIM on same:

http://btsc.webapps.blackberry.com/btsc/viewdocument.do;jsessionid=2D0498B9C4E295E8293D870182CADED2?...