Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10
11.6.0, 11.5.2, 11.5.0 HF4, 11.4.1 HF4
Opened: Jan 30, 2014
Related AskF5 Article: K15392
The following error messages are logged when a SDDv2 resync failure occurs in 11.4.0 or later: iSession: internal error: isession_rx_isession_msg:5561: Error parsing isession msg: ERR_NOT_FOUND iSession: internal error: isession_tdr2_rx_ctrl_dispatch:737: dispatching received SDDv2 control message: ERR_NOT_FOUND iSession: internal error: isession_dedup_rx_ctrl_conn:1672: processing received isession control message: ERR_NOT_FOUND
The distributed deduplication cache shared between two endpoints remains unsynchronized. Lack of cache synchronizaation may result in negative acknowledgement of deduplication hits due to data not being found in the cache.
When SDDv2 dedupliation is used between BIG-IP platforms that have different TMM thread counts (e.g. a BIG-IP 3900 and a BIG-IP 11000) cache resynchronization will fail after iSession tunnel aborts.
Manually forcing a cache refresh for a remote endpoint will reset the deduplication cache, but may terminate active iSession tunnels and will reduce the deduplication hit rate until the cache is repopulated.
SDDv2 cache resynchronization regression has been fixed.