Q: A persistence RULE is configured with a persistence timeout of 10 minutes. When "show persistent sessions" command is run for that particular load balancing vserver, many entries with a timeout of 0 (expired) are still see in the output table. What causes this persistence table entries to show even though the timeout  has expired? 

A: The "show persistence session" output only displays entry from master core and not from peer cores where persistence session is cached. Even if the timeout value is set to 0 on the master core, the other core still has this session entry with non-zero value due to which the master core does not remove this from its table immediately after it times out.

In order to further get information from each core you can use nsapimgr commands from Shell.

Q: A persistence RULE is configured with a persistence timeout of 10 minutes. When "show persistent sessions" command is run for that particular load balancing vserver, many entries with a timeout of 0 (expired) are still see in the output table. What causes this persistence table entries to show even though the timeout has expired?