Confine peristence table to one TMM and one SLOT to a viprion multiblade chassis
Hi to all, a customer need to have a Single Node Persistence configuration for a virtual service. I've followed the irule as listed here: https://devcentral.f5.com/wiki/iRules.SingleNodePersistence.ashx ad it worked until...... one blade of the cluster had a reboot..... so....
This is the persistence record before the reboot
show ltm persistence persist-records virtual devicecom-BB-2001-6 Sys::Persistent Connections universal 192.168.1.91%1158:2001 192.168.1.88%1158:2001 1/1 universal 192.168.1.91%1158:2001 192.168.1.88%1158:2001 1/0 universal 192.168.1.91%1158:2001 192.168.1.88%1158:2001 2/1 universal 192.168.1.91%1158:2001 192.168.1.88%1158:2001 2/0
This after the reboot
show ltm persistence persist-records virtual devicecom-BB-2001-6 Sys::Persistent Connections universal 192.168.1.91%1158:2001 192.168.1.88%1158:2001 1/0 universal 192.168.1.91%1158:2001 192.168.1.88%1158:2001 1/1 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
So BLADE1 with TMM1 and TMM2 use note .89 BLADE2 with TMM1 and TMM2 use node .89
I've tryed to use "cmp-enabled none" to the vitual to avoid this situation..but it won't work
Any suggestion? Shoud i use a differet irule?
Thanks