--> An iRule is a scripting language that we use to take the advantages of extra features of BIG IP system which are not available via CLI or GUI.
--> By default, BIG IP System sends the traffic to pool to which virtual server is associated with it.
--> By using iRules, it is possible to send the traffic specific to individual pool members, Ports, and URIs based upon the requirements.
--> iRules provides more advanced capabilities to F5 LTM in order to meet specific requirements in the network.
---> iRules is based upon programming language called Tool Command Language ( TCL).
--> iRules are not enabled until it is applied to the virtual server in BIG IP System.
--> Once iRules is enabled on the virtual server, it checks all the traffic passing via a virtual server.
--> iRules allows BIG IP System to modify server side and client side traffic all the way up to application layer.
---> With the help of iRules we can do following things but not limited to,
i) Load Balancing based upon Application Data
ii) Redirecting traffic based upon HTTP status codes
iii) Load Balancing based upon Country
iv) Load Balancing based on the type of browser or type of device
--> It is recommended to use an iRule is when you want to add some form of functionality to your application and that functionality is not already readily available via the built-in configuration options in your BIG-IP.
--> It is not recommended to use an iRule is any time you can do something from within the standard config options, profiles, GUI or CLI – do it there first.
--> If you’re looking to perform a task that can’t be accomplished via the “built-in” means of configuration, then it is a perfect time to turn to iRules to expand the possibilities.
--> A simple example of iRule is to redirect traffic from HTTP to https.
when HTTP_REQUEST {
HTTP::redirect "https://[HTTP::host][HTTP::uri]"
}
Ref: F5.com
Md.Kareemoddin
CCIE # 54759
--> By default, BIG IP System sends the traffic to pool to which virtual server is associated with it.
--> By using iRules, it is possible to send the traffic specific to individual pool members, Ports, and URIs based upon the requirements.
--> iRules provides more advanced capabilities to F5 LTM in order to meet specific requirements in the network.
---> iRules is based upon programming language called Tool Command Language ( TCL).
--> iRules are not enabled until it is applied to the virtual server in BIG IP System.
--> Once iRules is enabled on the virtual server, it checks all the traffic passing via a virtual server.
--> iRules allows BIG IP System to modify server side and client side traffic all the way up to application layer.
---> With the help of iRules we can do following things but not limited to,
i) Load Balancing based upon Application Data
ii) Redirecting traffic based upon HTTP status codes
iii) Load Balancing based upon Country
iv) Load Balancing based on the type of browser or type of device
--> It is recommended to use an iRule is when you want to add some form of functionality to your application and that functionality is not already readily available via the built-in configuration options in your BIG-IP.
--> It is not recommended to use an iRule is any time you can do something from within the standard config options, profiles, GUI or CLI – do it there first.
--> If you’re looking to perform a task that can’t be accomplished via the “built-in” means of configuration, then it is a perfect time to turn to iRules to expand the possibilities.
--> A simple example of iRule is to redirect traffic from HTTP to https.
when HTTP_REQUEST {
HTTP::redirect "https://[HTTP::host][HTTP::uri]"
}
Md.Kareemoddin
CCIE # 54759
0 comments:
Post a Comment