Glocal persistency with cookie

The rule was written to meet a requirement for clients who could not be persisted within the application (hardcoded 1minute refresh utilizing name only) The 3dns was configured to round robin, so client was redirected nearly every minute for data refresh, which caused real problems since the SLA on data sync on the backend was 5 minutes.

 

 

That aside, there is no assurance that the redirect will succeed. Also, what's missing above is that the vipid variable will be set with only a name, the class needs to be configured so that the vip IP can be extracted as a result of the supplied vip NAME. Otherwise, you'll end up with tcl errors.