It turns out that our Network Engineer had to create a route in our Cisco router (gateway) to route traffic to the vMotion network.  I was then able to configure the vMotion adapter and TCP/IP Stack correctly which allowed the vMotion and vStorage Motion to work.  Overall, due to the way our network was configured it wasn't a L3 solution that we ended up doing.  I'm trying to explain it the best I can on what I was told and learned along the way, but in the end...it's all good and it's working!  Thank you for your help.  It was just you and one other person from the VMware Community helping me out with this one...again...thanks.
We've recently installed a new VxRail S470 into our environment and my goal is to do live migrations using vMotion and vStorage Motion to move my existing VM's from our vCenter/SAN into the embedded vCenter that comes with VxRail/vSAN.  The one thing that I've tried is to make sure that all Level 3 connectivity between the two environments is enabled and I disconnected/removed a host from my existing environment and tried adding it to my VxRail/vSAN cluster, but due to EVC mode I'm needing to shutdown the service VM's on VxRail to then lower the EVC to be compatible with my existing host servers.  How do I go about doing this since I've read that the service VM's which includes vCenter are part of the VxRail shutdown process, so I'm wondering if there is a way to shutdown these VM's manually? If not, is there another better option?  I read an article on these forums that mentions doing the opposite which is adding the VxRail vCenter to my existing vCenter and then migrate my VM's to VxRail that way.  They are both running version 6.0, but not sure if the EVC will come into play in this scenario.  Both vCenter's are virtual appliances.  Any help would be appreciated as I'm trying to migrate to then retire my existing VMware environment.  The end result is running only my VxRail environment.  Thanks,  Angel
Migration of Existing VM's to VxRail