How would I use a Table as a global cross tmm variable to be CMP compliant?

I think there is a miss understanding in what I'm been asked to accomplish. I understand the pool selection process can be accomplished by standard F5 configuration. What I need to accomplish is:

1.) Client starts NFS or CIFS connection to VIP

2.) VIP selects primary_pool and sends traffic to that pool. 3.) If primary_pool is down:

3.a) Send kill command for all F5 sessions associated with VIP

3.b) Have F5 send command to Secondary storage pool master to kill backend sync jobs

3.c) wait 5 seconds

3.d) Activate write on secondary storage cluster

4.) Send all connections to secondary cluster.

5.) On recovery of primary cluster manual fail back is desired.

The variable I'm using is a flag so globally the traffic across all sessions only have steps 3.a - 3.d performed once on a fail over. Note: Fail over only occurs if the primary storage pool has <2 pool members.

Everything functions but its not optimized. When I use static TCL variables or Global Variables the iRule is demoted from the CMP meaning only 1 of 8 cores is used for these transactions.