Had the same issue when trying with our CSS, switched to A/P cluster. UDP is not intercepted and processed by the CSS the same as TCP because it is a stateless and connection less protocol. We could not get out CSS to maintain a UDP "connection" table for the UDP connections like it does with the TCP conncection. The CSS documentation describes a way to do this but we could not get it to work with our configuration. If you use a service group on the CSS, then the IP of all requests to the SA will be the CSS IP becuase it NATs the client IP to itself and forwards the packet onto the selected SA. Maybe then the UDP packets will come back to the CSS and then be returned to the client instead of the SA trying to communicate directly back to the client. The key is that the CSS must register and monitor client connection mappings for UDP.
... View more