If I'm understanding your configuration correctly, traffic destined to a VIP on the CSS that contains services in the 10.5.1.0/24 VLAN would likely be routed back out the front-side of the CSS (or wherever the default route goes) if the CSS is not IP'd from the 10.5.1.0/24 subnet. Or, you can have a static route to the 10.5.1.0/24 subnet on the CSS to go out the backend interface.
Are you using 'add destination service' in your source group rule? If so, the CSS will NAT the client's address as whatever address you have specified in the group rule, and then send traffic to the service chosen for load balancing. The return traffic would then come back to the CSS, the NAT reverted, and then sent back to the client. Because of this, you'll never see the true client source IP on your server. Only the IP specified in the group rule.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...