User access to limited irules.

Yes, you can create a new partition called A and create a new user with role iRule Manager and just select this A partition.

As for moving the existing iRule configuration. If you are pre TMOS 11.6 then the only way around this is to delete the iRule and recreate in the new partition or edit the bigip.conf file via SSH. If you've 11.6 then there's a new feature to move objects. See 11.6 release notes and the section "Object move and rename". I've not used this feature myself so I'd test first.

Hope this helps,

N

Hi Nathan,

Thanks for your help.

Cheers!

Hi Nathan,

Also this is what my requirement is. Do you have any comments ?.

Assume I create an irule list(located on common par) where will call the datagroup list (located on different partition). Is it possible? If yes, does the syntax also the same? Here is some syntax irule we use when CLIENT_ACCEPTED { if { [class match [IP::client_addr] equals userA] } { snatpool snat-userA return elseif { [class match [IP::client_addr] equals userB] } { snatpool snat-userB return } else { snatpool snat-userdefault } }

Where we assume usera and snat-userA will located on partition a userb and snat-userB will located on partition b while snat-userdefault and the irule will located on common partition

Hi Nathan,

Also this is what my requirement is. Do you have any comments ?.

Assume I create an irule list(located on common par) where will call the datagroup list (located on different partition). Is it possible? If yes, does the syntax also the same? Here is some syntax irule we use when CLIENT_ACCEPTED { if { [class match [IP::client_addr] equals userA] } { snatpool snat-userA return elseif { [class match [IP::client_addr] equals userB] } { snatpool snat-userB return } else { snatpool snat-userdefault } }

Where we assume usera and snat-userA will located on partition a userb and snat-userB will located on partition b while snat-userdefault and the irule will located on common partition

From the tmos concepts guide, "an iRule can reference any object, regardless of the partition in which the referenced object resides. For example, an iRule that resides in partition my_app_A can contain a pool statement that specifies a pool residing in partition my_app_B. Neither object is required to reside in Common"

Hope this helps

From the tmos concepts guide, "an iRule can reference any object, regardless of the partition in which the referenced object resides. For example, an iRule that resides in partition my_app_A can contain a pool statement that specifies a pool residing in partition my_app_B. Neither object is required to reside in Common"

Hope this helps