It is hard to tell without seeing a sniffer trace what is going on, but to me, it sounds like some flavor of non symetric traffic flow. ACE will not accept traffic from a source MAC that is knows is configured elsewhere on its own physical blade/chassis. Routing it should resolve this as you are trying to do. However, there are a few gotachas about that. ACE expects to recieve traffic symetrically, so if the server can see context A directly and does not have to follow a path back through the routers to get to it, this won't work (use source NAT on context A and B to control flow of traffic in that scenario.) As well... ACE will not route what it can see is already L2 adjacent in its connection table. If either context sees the next hop, it won't route the traffic even with a static route there.
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
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...