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

I think in this instance you might be better off using Priority Group Activation rather than an iRule. PGA will continue to work regardless of 'local' failure events such as a blade reboot. Of course, I'd suggest you do some research on it's behaviour before proceeding.

Generally the downside compared to this rule is that traffic will return to a member that went down when it returns to service, unless you configure Manual Resume, in which case manual intervention is required to restore resilience (assuming two Pool Members). In other words, with Manual Resume, the failure of both nodes (together or at different times) would render the service unavailable (without manual intervention).