Forum Discussion

Misty_Spillers_'s avatar
Misty_Spillers_
Icon for Nimbostratus rankNimbostratus
Feb 14, 2013

Exchange iapp for multiple Exchange servers (different customers)

I'm on version 11.2.1 and using f5.microsoft_exchange_2010_cas.2012_06_08.     I created an "APM will provided secure remote access" iapp for one of our customers and it worked for the most p...
automation
devops
iApps
management
TMSH
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Jun 19, 2013
    Misty,

     

    This morning I successfully tested deploying two separate Exchange environments behind a single BIG-IP running APM. I can think of at least two features required by this solution that are only available in BIG-IP v11.3 and above, which are the AAA server pool and client-initiated forms SSO.

     

     

    You will also want to use the latest version of the iApp, RC3, which we expect to release in the next day or so. Can you send me a private message on DevCentral with your email contact info? I can let you know as soon as that RC has been declared.

     

    Mike
speedbird_86757's avatar
speedbird_86757
Icon for Nimbostratus rankNimbostratus
Jul 31, 2013
Mike,

 

 

As suspected, our issue was the SNAT pool configuration. The iApp creates an iRule with the $Name chosen by us, but within the iRule, the array name still needs to be unique across the different iApps.

 

 

For example:

 

**********

 

when RULE_INIT {

 

set static::iAppFoo_snat_ips(0) 1.1.1.1%816

 

set static::iAppFoo_snat_ips(1) 1.1.1.2%816

 

}

 

when CLIENT_ACCEPTED {

 

snat $static::iAppFoo_snat_ips([expr {[crc32 [IP::client_addr]] % [array size static::iAppFoo_snat_ips]}])

 

}

 

 

**********

 

Maybe this could be enhanced in the next iApp version? For now, we've worked around the problem by manually renaming the values within the iRule.

 

 

Thanks for your help.