Forum Discussion

Yuval_ben_10707's avatar
Yuval_ben_10707
Icon for Nimbostratus rankNimbostratus
Jun 14, 2005

iRules documetation

Hi,

 

 

I'll appriciate if you can provide a direct link to the iRules documentation (including BigIP verbs).

 

I could find the iControl docs but not iRules.

 

 

Thanks
application delivery
dev
devops
iRules
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Jun 14, 2005
    Currently the iRules documentation is included in the BIG-IP product manuals (available at http://tech.f5.com). We've made Tech Tips into most of that content here at DevCentral. Take a look at the "Tech Tips - Rules" section on the "Docs and Tips" page.

     

     

    I'm working on a iRules cheat sheet but it's proving difficult to get through the 100's and 100's of available methods and put them all in proper context (serverside, clientside, available events, readonly, readwrite, etc). I may just release this document as a starting point with some possible known issues. Keep an eye out on the iRules forums (Click here) or my blog (Click here) for a notice when it's available.

     

     

    -Joe
  • Brian_Gupta_115's avatar
    Brian_Gupta_115
    Icon for Nimbostratus rankNimbostratus
    Sep 27, 2005
    I am trying to wrap my head around these events, and their default contexts. I listed some of the events below and categorized them by the context that I felt was the most intuitive default context.

     

     

    Could someone please let me know if my categories match reality?

     

     

    Global Context:

     

    ---------------

     

    RULE_INIT - Triggered when you add or modify a iRule. You use this event to initialize global variables that you are using within iRules. Please note that this event is triggered even if the rule is not yet in use.

     

     

    Client Context:

     

    ---------------

     

    CLIENT_ACCEPTED - Triggered when a client establishes a connection.

     

    CLIENT_DATA - Triggered when a client receives new data while the connection is in collect state.

     

    CLIENT_CLOSED - Triggered when the client's connection is closed.

     

     

    Server Context:

     

    ---------------

     

    SERVER_CONNECTED - Triggered when the system establishes a connection with the target node.

     

    SERVER_DATA - Triggered when the system has received new data from the target node while the connection is in hold state.

     

    SERVER_CLOSED - Triggered when the server's connection is closed.

     

    SERVER_SELECTED - Please note this command has been replaced by LB_SELECTED Triggered when the LTM system has selected a target node.

     

    LB_SELECTED - Triggered when the LTM system has selected a target node.

     

    LB_FAILED - Triggered when a connection to the server was unable to complete. This might occur if the pool has no available members or a selected pool member is otherwise not available.

     

     

    Thanks,

     

    Brian