I ran into a similar issue with asymmetric routing when I first set up my multi-homed vCloud cells. In my case the IP for each interface was on a different subnet, but the approach is the same for your scenario. You need to add some policy based routing rules using iproute2 commands.
Here's a great article that describes the problem and the solution: http://www.linuxjournal.com/article/7291
For your issue you probably want something like this:
Cell01:
/sbin/ip route flush table 1
/sbin/ip route flush table 2
/sbin/ip route add default via <gateway-ip> dev eth0 table 1
/sbin/ip route add default via <gateway-ip> dev eth1 table 2
/sbin/ip rule add from 192.168.1.1/32 table 1 priority 500
/sbin/ip rule add from 192.168.1.11/32 table 2 priority 600
Cell02:
/sbin/ip route flush table 1
/sbin/ip route flush table 2
/sbin/ip route add default via <gateway-ip> dev eth0 table 1
/sbin/ip route add default via <gateway-ip> dev eth1 table 2
/sbin/ip rule add from 192.168.1.2/32 table 1 priority 500
/sbin/ip rule add from 192.168.1.12/32 table 2 priority 600
Good luck!
