Hello Sai,
So what is the full command you're using? If I'm understanding correctly, you want vmk3 to use it's own gateway for all traffic. That's fine,- you'll simply use one static route for every subnet you want to originate at vmk3. It looks like you're using the following command. If so, it's not what you want.
esxcli network ip route ipv4 add -g 10.28.187.253 -n 10.28.184.0/22
The command above says tells ESXi, "if you want to reach the 10.28.184.0/22 network, use the gateway 10.28.187.253." And vmk3 is already on that network.
You want to replace the subnet portion of that command with the destination network you want to reach. You'll want something like
esxcli network ip route ipv4 add -g 10.28.187.253 -n 192.168.10.0/24
Where 192.168.10.0/24 is the subnet you want to reach via vmk3. This can be considered a bad thing if you have many subnets to reach from vmk3, because that's many static routes on each host. But it should work.
Can you share the full command you were using?
Thanks,
Mike
-----------------------------------------
Please consider marking this answer "correct" or "helpful" if you found it useful.
Mike Brown
VMware, Cisco Data Center, and NetApp dude
Consulting Engineer
Twitter: @VirtuallyMikeB
Blog: http://VirtuallyMikeBrown.com
LinkedIn: http://LinkedIn.com/in/michaelbbrown