Estamos com o mesmo problema mas, na versão 4.27.
Resposta da Cisco para nós:
The bad news is that the developers state, in this specific moment, there is not a workaround to fix this particular problem with CSM.
The good news is that there is a permanent fix for this problem, but it will be available on CSM version 4.30. Of course, I have asked to our engineering team if there is an approximate date for this version to be released. As soon as I have this information, I will let you know immediately.
