For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

ewest111's avatar
ewest111
Icon for Nimbostratus rankNimbostratus
Nov 05, 2015

Exchange 2013 Pool

I have asked this question once before but after doing the software update on my BIG IP LTM I'm back to the same scenario and can't get it figured out. Using the latest template I have created an iA...
application delivery
availability
deployment
devops
iApps
LTM
Henrik_Gyllkran's avatar
Henrik_Gyllkran
Icon for Nimbostratus rankNimbostratus
Nov 06, 2015

This sounds like a persistence issue, the reason why you see the logon page again and again is that you log on to one server and is then loadbalanced to the other CAS which doesn't recognize the session from the first server so it presents the logon page. You log on and is then loadbalanced to the first server which doesn't recognize the session from server 2 and so on...

 

Now, I know that Exchange 2013 shouldn't need persistence but I've seen a whole bunch of Exchange implementations that needed Persistence to work just the same. Now in regards to why it stopped working after the upgrade that's a mystery.