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

Rabbit23_116296's avatar
Rabbit23_116296
Icon for Nimbostratus rankNimbostratus
Jan 20, 2014

Issue with latest Exchange iApp template? invalid irule?

01220001:3: TCL error: /Common/_sys_APM_Exchange - Illegal argument. Invalid client side API (line 6) invoked from within "HTTP::status"

 

from the LTM log this is continuously logged, I notice this irule does not exist in my common partition and don't believe, if it is an irule trying to call this method, that it is part of the new iApp template.

 

3 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Jan 20, 2014

    So you don't see this iRule anywhere in the GUI/iRules bit? What TMOS version are you running and are you running the latest 1.2.0 iApp? I see from the Exchange iApp deployment guide it has this note "If using the Exchange profile in 11.4 and later, you must remove any _sys_APM irules from the virtual server"

     

    Not sure if that's relevant as I've not got APM in the lab to test I'm afraid.

     

    Rgds

     

    N

     

  • Rabbit23_116296's avatar
    Rabbit23_116296
    Icon for Nimbostratus rankNimbostratus
    Jan 20, 2014

    using 11.4.1 and latest iApp yes. There are other *sys_apm irules present but yes none are actually bound to the virtual server..

     

  • Rabbit23_116296's avatar
    Rabbit23_116296
    Icon for Nimbostratus rankNimbostratus
    Sep 02, 2014

    So on this load balancer this issue still persists. This is after upgrading to 11.5.0 and to the latest Exchange template 1.3.0. This is only happening on this load balancer and not its partner in the opposing DC.

    I suspect it's a bug and its causing issues with EWS and Outlook Anywhere. How could I work around it, I suspect it's a version of the iRule that used to live in Common partition that now appears compiled into the APM Exchange config:

     when HTTP_RESPONSE_RELEASE {
        if { ! [info exists user_key] } {
            return
        }
        log -noname accesscontrol.local1.debug "$static::ACCESS_LOG_PREFIX HTTP response: status:           [HTTP::status]"
        log -noname accesscontrol.local1.debug "$static::ACCESS_LOG_PREFIX HTTP response: Server:           [HTTP::header Server]"
        log -noname accesscontrol.local1.debug "$static::ACCESS_LOG_PREFIX HTTP response: Content-Length:   [HTTP::header Content-Length]"
        log -noname accesscontrol.local1.debug "$static::ACCESS_LOG_PREFIX HTTP response: WWW-Authenticate: [HTTP::header WWW-Authenticate]"
    }