Forum Discussion

hooleylist's avatar
hooleylist
Icon for Cirrostratus rankCirrostratus
Oct 04, 2007

New iRule features in 9.4.2?

Can anyone elaborate on any new iRule features in 9.4.2? I've seen reference to enabling or disabling a plugin using PLUGIN::disable [plugin name].

 

 

Are there any new events? Are there any other new toys?

 

 

Thanks,

 

Aaron

7 Replies

  • AFAIK, there isn't really anything worth mentioning other than SCTP events - but they are up on Wiki.
  • spark_86682's avatar
    spark_86682
    Historic F5 Account
    There were actually several new iRule tools added into 9.4.2. I'll have to check to see what info is OK to release, which will take me a few days...
  • spark_86682's avatar
    spark_86682
    Historic F5 Account
    OK, I've cleared the list of new iRule features in 9.4.2. This is mostly just an overview of them, I'm not going to attempt to really document them here. More complete info should appear in the Wiki over the next few months. Here's the list:

     

     

    New events:

     

    *) PERSIST_DOWN (fires when a persistence entry would send a request to a down node)

     

    *) CACHE_UPDATE (fires when a cache entry is updated, presumably)

     

    *) SIP_RESPONSE_SEND (analogous to the HTTP_REQUEST_SEND event, I think)

     

     

    New commands:

     

    *) Many SCTP:: commands (already in the Wiki)

     

    *) SIP::payload command (for accessing the SIP payload, ala TCP::payload)

     

    *) CACHE::fresh (Returns true or false, indicating if the document is fresh (is cached and not stale))

     

    *) CACHE::statskey (Sets the stats bucket for the cached document, to provide statistics in user-defined groups)

     

    *) CACHE::header {insert, value, remove, replace, exists} commands (analogous to the HTTP::header commands, but for cached documents)

     

     

    Updated commands:

     

    *) active_members (and active_nodes) now take the "-list" parameter, which will return a TCL list of the active members (this is a long-requested feature).

     

    *) matchclass and findclass can now use classes without requiring the "$::" prefix. This is to allow classes on CMP-enabled VIPs. (Without this change, the "$::" prefix would make the BIG-IP system believe a global variable was being referenced, which would disqualify the VIP from running in CMP mode.)

     

    *) HTTP::response now can have the "noserver" keyword after the code parameter. This specifies that the "Server: BIG-IP" header won't be inserted.
  • Thanks for the info. The updated command section has some nice to features.

     

     

    Aaron
  • Posted By spark on 10/29/2007 5:49 PM

     

     

    Updated commands:

     

    *) matchclass and findclass can now use classes without requiring the "$::" prefix. This is to allow classes on CMP-enabled VIPs. (Without this change, the "$::" prefix would make the BIG-IP system believe a global variable was being referenced, which would disqualify the VIP from running in CMP mode.)

     

     

    So instead of using $::class should I now use $class or just class?

     

     

  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    You can continue to reference them with the $:: prefix, or with none at all to allow the VS to leverage CMP:

     

     

    $::class_name or class_name