Forum Discussion

Joshua_Bines_12's avatar
Oct 19, 2016
Solved

MAPI-over-HTTP 11.6 Adding the irule

Hi All,

 

Just wanted to confirm use of the Exchange 2016 iAPP for MAPI-over-HTTP on TMOS 11.6

 

I have created the irule (Pg 90 deployment guide) used the existing MAPI pool from the iapp but I read that could add the irule via the iapp I just don't see that option?

 

I have disabled strict updates and added it to the combined VS but autodiscover ews etc is now failing with no sessions created on the APM

 

Thanks Joshua Bines

 

  • Under the option in the iapp

     

    Do you want to customize your server pool settings? select "Customize pool settings"

     

    This adds the option

     

    Do you want to add any iRules to this combined virtual server?

     

    Worked a treat

     

4 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi Joshua, the Exchange 2016 iApp should have all the necessary objects for MAPI-over-HTTP built in. Can you tell me what the version number is on the copy of your iApp?

     

    • Joshua_Bines_12's avatar
      Joshua_Bines_12
      Icon for Cirrus rankCirrus

      Hi Mike,

       

      exchange 2016 v1.0

       

      On the deployment guide is suggests below. pg 90

       

      If using APM v11.x only: Because BIG-IP APM is not yet supported for MAPI over HTTP in v11.x, the iRule in the following table includes a line (commented out by default) to disable Access Policy processing for this new protocol only. If you configured the iApp to use separate virtual servers, you create the monitor, pool, and a virtual server. The iRule is not necessary at all in this case.

       

  • Under the option in the iapp

     

    Do you want to customize your server pool settings? select "Customize pool settings"

     

    This adds the option

     

    Do you want to add any iRules to this combined virtual server?

     

    Worked a treat

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Sorry, it didn't register with me that you are on v11.6 (APM is fully supported for MAPI-over-HTTP in 12.0 and later).

    The Exchange 2016 iApp handles the traffic, but APM won't work, so you should use this iRule. You should not have to disable strictness; instead, create the iRule and then reconfigure the iApp to attach the rule to the virtual server.

    when HTTP_REQUEST {
     switch -glob -- [string tolower [HTTP::path]] {
     "/mapi*" {
     ACCESS::disable
     }
     }
    }