Linking Universal persistence across different dataflows and virtual servers

Thanks nitass, I've been trying to think along the same lines looking into session commands. I had another thought this morning ( based of what I've read, but i may have massively over simplified it) and i need to test the theory in the lab.

 when CLIENT_DATA {
  USER MAC - radius attribute 31 Calling-Station-Id
  client-IP - radius attribute 8 Framed-IP
  persist based on MAC found in the radius traffic, if exists use it, else create a new one and loadbalance as normal.
 persist uie [RADIUS::avp 31] }
 
when LB_SELECTED {
create persist rule for current server but using framed IP or client-IP as the identifier
persist add uie "[RADIUS::avp 8] pool pool1" 1800}

when CLIENT_DATA {
 If persist exists for client IP use it, otherwise create a new one and loadbalance as normal.
persist uie [IP::client_addr]}