F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Mariusz_B's avatar
Mariusz_B
Icon for Nimbostratus rankNimbostratus
Feb 17, 2015

iRule - wrong variable definition ?

Hi all, I have the following iRule, which in terms of syntax is fine: when DNS_REQUEST { switch [IP::remote_addr] { "10.10.1.32/27" - "10.10.1.64/27" - "10.10.1.16...
application delivery
BIG-IP DNS
devops
iRules
Mariusz_B's avatar
Mariusz_B
Icon for Nimbostratus rankNimbostratus
Feb 26, 2015

Hello all,

 

Sorry for the delay with my feedback and thank you everyone for help. I managed to get some help from highly skilled iRule engineer, and below I am placing the final version. The biggest advantage of the iRule is that adding more clients, doesn't require any code modification. All I have to do is to modify 2 data groups; one called Clients_IPs (which is going to be universal, and which will be created for each wide IP.

 

when DNS_REQUEST {
 set mon "[class match -value [IP::remote_addr] equals Clients_IPs]"
 set ip "[class match -value  [DNS::question name] equals www.test.com_IP]"
 if { ( $mon ne "" ) && ( $ip ne "" ) } {
  if {[LB::status vs $mon up]} {
     host [getfield $ip "," 1]
   } else {
   host [getfield $ip "," 2]
   }
 }
}

Regards

 

Mariusz

 

Mariusz_B's avatar
Mariusz_B
Icon for Nimbostratus rankNimbostratus
Feb 27, 2015
Yes, you're right. Probably www.test.com_IP is not necessary. To simplify I can hardcode the IPs. I have to create separate iRule for each Wide IP anyway. This is good if you expect your IP to be change in the future. In this case you don't have to interfere with the iRule code. Cheers