Forum Discussion

scarpozzi_82104's avatar
scarpozzi_82104
Icon for Nimbostratus rankNimbostratus
Sep 15, 2011

iRules executing on Virtual Servers they're not applied to?

BIG-IP 10.2.0 Build 1755.1 Hotfix HF1

 

 

I've got a few iRules that I use for various things. Mostly, I created 2 or 3 iRules for setting up a Maintenance window and did some reading yesterday for stream profiles/html content rewriting.

 

 

I've got 4 virtual servers that are split into 2 sites....one for testing, one for production:

 

 

http/https dev

 

http/https prod

 

 

When testing the stream profile yesterday, I noticed that I could add the blank stream profile to the dev/prod virtual servers. Then apply the iRule to ONLY the dev http/https virtual servers and the rewrite would STILL happen on the prod virtual servers.

 

 

Can anyone give me any idea why that might be happening? It's not a big deal...I was watching for it because I was in the process of testing. I just want to know if anyone else has seen this kind of behavior and if there's a way to prevent it. When I apply an iRule to a virtual server, I expect it to be set for only that virtual server and not every virtual server...
application delivery
dev
devops
iRules
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Sep 15, 2011
    If you add a stream profile with any configuration it will perform the find/replace operation on request and response payloads without an iRule. Is this the scenario you were seeing?

     

     

    Aaron
  • scarpozzi_82104's avatar
    scarpozzi_82104
    Icon for Nimbostratus rankNimbostratus
    Sep 15, 2011
    The stream profile was actually blank. I wanted the flexibility of leaving it up to the iRules to define where and what gets rewritten. I've just had some instances where things overlap between these virtual servers.

     

     

    The iRule itself is where the find/replace operations were defined.

     

     

    Looking back, I think I know what happened. I had the iRule on all virtual servers originally and removed it from the production environment. I'm guessing the configuration settings were still being cached when I was doing testing. It appears to be working normally now. I usually run a config sync to trigger the config to reload when I'm done making changes.