Lync MAPI Connectivity Into Exchange (UcMAPI.exe)

Well, this is a good one! Apparently, the pool statements in this Persistence iRule are meant to cover more than just circumstances where a single Virtual Server is used.

After changing to the shortened iRule above, we get the aforementioned errors in the APM log along with a single persistence record created WITHOUT A Pool to member IP 127.20.2.254:10001. This record goes idle immediately and expires at the inactivity timeout count.

When I restored the Persistence iRule back to the following (inclusive of pool statements), we no longer saw this issue:

when ACCESS_ACL_ALLOWED {
    set sessionid [ACCESS::session data get "session.user.sessionid"]
    switch -glob -- [string tolower [HTTP::path]] {
        "/microsoft-server-activesync*" {
            pool APM_EXCHANGE2010_as_pool2
            persist uie $sessionid 1800
            return
        }
        "/owa*" {
            pool APM_EXCHANGE2010_owa_pool2
            persist uie $sessionid 1800
            return
        }
        "/ews*" {
            pool APM_EXCHANGE2010_oa_pool2
            persist uie $sessionid 1800
            return
        }
        "/ecp*" {
            pool APM_EXCHANGE2010_owa_pool2
            persist uie $sessionid 1800
            return
        }
        "/oab*" {
            pool APM_EXCHANGE2010_oa_pool2
            persist uie $sessionid 1800
            return
        }
        "/rpc/rpcproxy.dll*" {
            pool APM_EXCHANGE2010_oa_pool2
            persist uie $sessionid 1800
            return
        }
        "/autodiscover*" {
            pool APM_EXCHANGE2010_ad_pool2
            persist none
            return
        }
        default {
             This final section takes all traffic that has not otherwise
             been accounted for and sends it to the pool for Outlook Web
             App
            pool APM_EXCHANGE2010_owa_pool2
            persist uie $sessionid 1800
        }
    }
}

when HTTP_RESPONSE {
    if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {
        ONECONNECT::reuse disable
        ONECONNECT::detach disable
        NTLM::disable
    }
    if {[HTTP::header exists "Transfer-Encoding"]} {
        HTTP::payload rechunk
    }
}
definition-checksum f41bb1953d96f40c57b91ae927bcaa4f

Does anyone know what would be happening with this strange IP? I'm just curious at this point as I seem to have corrected my own foul-up. 🙂

-Cory