Confine peristence table to one TMM and one SLOT to a viprion multiblade chassis

I've cheked ..... Now i got in Cluster Option -> Network mirroring withing Cluster.

This is the virtual server config:

ltm virtual virtual-1-36ZF7UD.FloatingLoadBalancer.LB_Device-FB-2001-6-4566 {
cmp-enabled no
destination 10.23.153.205%4566:2001
ip-protocol tcp
mask 255.255.255.255
persist {
    persistence_PriorityFailover {
        default yes
    }
}
pool pool-1-36ZF7UD.FloatingLoadBalancer.LB_Device-FB-2001-6-4566
profiles {
    fastL4 { }
}
snat automap
vlans-disabled
}

ltm pool pool-1-36ZF7UD.FloatingLoadBalancer.LB_Device-FB-2001-6-4566 {
members {
    node-10.23.153.197-4566:2001 {
        address 10.23.153.197%4566
        priority-group 1
        session monitor-enabled
        state up
    }
    node-10.23.153.199-4566:2001 {
        address 10.23.153.199%4566
        priority-group 1
        session monitor-enabled
        state up
    }
}
monitor tcp-5-16 
service-down-action reselect
}
ltm persistence universal persistence_PriorityFailover {
app-service none
defaults-from universal
rule ARIWATCH-PriorityFailover
timeout 7200
}
ltm rule ARIWATCH-PriorityFailover {
when CLIENT_ACCEPTED { persist uie 1 }
}

So, you tell me that , since the mirror persistence is not enabled, the cluster (blade 1 and blade 2) does not share the same persistence records? So why in normal conditions (blade1 and blade2 in cluster) the persistence is binded always to one server or the onother? See above ( 192.168.1.89)

show ltm persistence persist-records virtual virtual-1-2VUMQQU.FloatingLoadBalancer.devicecom-BB-2001-6
Sys::Persistent Connections
universal  192.168.1.91%1158:2001  192.168.1.89%1158:2001  2/0
universal  192.168.1.91%1158:2001  192.168.1.89%1158:2001  2/1
universal  192.168.1.91%1158:2001  192.168.1.89%1158:2001  1/0
universal  192.168.1.91%1158:2001  192.168.1.89%1158:2001  1/1
Total records returned: 4*

M.G.