Applies To:

Show Versions Show Versions

Manual Chapter: Managing iRules
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

How do I change object settings on a managed device?

To change the object settings on a managed device, there are four tasks to perform.

This figure illustrates the workflow you perform to manage the objects on BIG-IP® devices. Changing the settings is the second step in this process.

Workflow for changing object settings on a managed device

Change managed object workflow

Create a new iRule

You can use the BIG-IQ® Local Traffic interface to add a new iRule to a managed device.
Important: When revising configurations on devices that belong to a high availability cluster, it is important to let the changes synchronize to the cluster members instead of trying to make the same changes to multiple devices. If you try to replicate changes you made on one device in the cluster, the next config sync attempt could fail.
Important: Rules are different from most other Local Traffic objects in that they associate with virtual servers instead of devices. So to deploy a new iRule to a device, you attach the iRule to a virtual server associated with the target device and then deploy that change.
  1. At the top of the screen, click Configuration.
  2. Under LOCAL TRAFFIC, select iRules.
    The screen displays a list of iRules® that are known on this device.
  3. Click Create.
    The New iRule screen opens.
  4. For Name, type a name for the iRule you are creating.
  5. For Partition, type the name of the BIG-IP device partition on which you want to create the iRule.
  6. For the Body, compose the script sequence that defines the iRule.
    For guidance on creating an iRule, consult the AskF5™ (support.f5.com) Knowledge Base. You can search the AskF5 website for iRules documentation that provides an overview of iRules, lists the basic elements that make up an iRule, and shows some examples of how to use iRules.
  7. Click Save & Close.
    The system creates the new iRule with the settings you specified.
To deploy this iRule to a device, attach the iRule to a virtual server associated with the target device and then deploy that change.

Attach iRules to virtual servers

You can use the BIG-IQ® Local Traffic interface to attach iRules® to a set of virtual servers. Adding an iRule sequence to a group of servers at once can save time and help you cut down on errors that result from performing repetitious tasks.
  1. At the top of the screen, click Configuration.
  2. Under LOCAL TRAFFIC, select Virtual Servers.
    The screen displays the list of virtual servers defined on this device.
  3. Select the check boxes associated with the virtual servers to which you want to attach iRules.
  4. Click Attach iRules.
    The Bulk Attach iRules screen opens.
  5. To specify which iRules to attach to the selected virtual servers, select them in the Available iRules list, and move them to the iRules to be Attached list.
  6. Specify the order in which you want the iRules to attach using the up and down arrows.
  7. For Location, specify the list position to attach these iRules.
    • To add the rules to the beginning of the existing list, click Attach to top of each virtual server's iRules list.
    • To add the rules to the end of the existing list, click Attach to bottom of each virtual server's iRules list.
  8. Use the Duplicate Policy setting to specify whether to keep the iRule list order for iRules that are already attached to the virtual servers.
    • To keep the existing list order, click Keep virtual servers' existing rules list order.
    • To change the existing list order to what you specified previously, click Reorder virtual servers' existing rules to preserve selected rules order.
  9. Click Save & Close.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)