Forum Discussion

Rene_C_'s avatar
Rene_C_
Icon for Nimbostratus rankNimbostratus
Jun 04, 2014

Proc Calls in different partitions

Hi,   in our Environment we got our Development and Quality/Staging Environment on one F5 BigIP, but on different partitions.   As we rely on iRules for our SSO-integration this leads to a stra...
application delivery
devops
iRules
LTM
partitions
proc call
nitass's avatar
nitass
Icon for Employee rankEmployee
Jun 04, 2014

this is my testing.

 version

root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) show sys version|grep -A 6 Package
Main Package
  Product  BIG-IP
  Version  11.5.1
  Build    0.0.110
  Edition  Final
  Date     Wed Mar 12 15:44:53 PDT 2014

 config

root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual /p1/v1
ltm virtual /p1/v1 {
    destination /p1/172.28.24.201:80
    ip-protocol tcp
    mask 255.255.255.255
    partition p1
    profiles {
        http { }
        tcp { }
    }
    rules {
        /p1/r1
    }
    source 0.0.0.0/0
    vs-index 42
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm rule /p1/r1
ltm rule /p1/r1 {
    partition p1
    proc pcure {} {
  log local0. "p1"
}
when HTTP_REQUEST {
  call pcure
  HTTP::respond 200
}
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual /p2/v2
ltm virtual /p2/v2 {
    destination /p2/172.28.24.202:80
    ip-protocol tcp
    mask 255.255.255.255
    partition p2
    profiles {
        http { }
        tcp { }
    }
    rules {
        /p2/r2
    }
    source 0.0.0.0/0
    vs-index 43
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm rule /p2/r2
ltm rule /p2/r2 {
    partition p2
    proc pcure {} {
  log local0. "p2"
}
when HTTP_REQUEST {
  call pcure
  HTTP::respond 200
}
}

 test (10 requests to /p1/v1 and another 10 requests to /p2/v2)

[root@ve11a:Active:In Sync] config  tail -f /var/log/ltm
Jun  4 03:00:14 ve11a info tmm[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm1[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm1[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm1[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm1[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:14 ve11a info tmm1[9801]: Rule /p1/r1 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm1[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm1[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm1[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm1[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm[9801]: Rule /p2/r2 HTTP_REQUEST: p1
Jun  4 03:00:17 ve11a info tmm1[9801]: Rule /p2/r2 HTTP_REQUEST: p1