F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Aaron_Warner_11's avatar
Aaron_Warner_11
Icon for Nimbostratus rankNimbostratus
Apr 30, 2013

Issue with Exchange 2010+ federation on BIGIP VE LTM+APM

Environment   Exchange 2010 Org   Published Via TMG 2010     Exchange 2013 Org   Published via BIGIP VE LTM+APM     Outlook anywhere is configured for basic authentication on...
microsoft
partner
Michael_Koyfma1's avatar
Michael_Koyfma1
Icon for Cirrus rankCirrus
May 01, 2013
I see. I have an idea now... I think the fact that first iRule triggers, and you call ACCESS::disable from there, which effectively SHOULD disable calls to all ACCESS events that are in the modified _sys iRule. So when the desired request gets to the mod_sys iRule, you trap it there and exit out of HTTP_REQUEST event, and all other events don't fire due to APM being disabled before. That's my guess - I will try to verify it. Do you mind removing ACCESS::disable command from the modified iRule and see if it will still work with both iRules assigned? If it does, I think it will confirm my theory.