BigIP-F5 iRule Concepts

Below are the customes of iRule which are very much used in BIG-IP F5 iRules labs

Customize traffic management to meet specific needs
Direct traffic based on content data
Event driven and Tcl-based

Below is the Syntex of BigIP F5 iRule:

when EVENT { if { conditional_expression } { action_when_condition_true } else { action_when_condition_false } }

iRule Operators

Below are BIG-IP F5 iRules Operators that are very much used in writing iRule Scripts:

Relational operators
- contains
- matches
- equals
- starts_with
Logical operators
- not
- and
- or

iRule Event Example

Pool Based Selection Example

rule BrowserType { when HTTP_REQUEST { if { [[HTTP::header User-Agent] contains “MSIE”] } { pool /Common/IE_pool } elseif { [[HTTP::header User-Agent] contains “Mozilla”] } { pool /Common/Mz_pool } } }

Profile Prerequisites for Certain iRule Events

iRule Event Groups

Various points client-server communication
Protocol
- IP TCP UDP SCTP
Application
- HTTP RTSP SIP XML
Security and Access
- APM ASM AUTH CLIENTSSL SERVERSSL
Other
- CACHE DNS GLOBAL STREAM

Comment

You are will be the first.

Please login here to comment.

EMAIL SUPPORT

LOCATION

BigIP-F5 iRule Concepts