I've stumbled on a resolution( it looks like that now anyway ) to the issue mentioned above.Simply shutdown the simulator & change the setting of the 8.1.0-38015 VM back to 4GB ( one data mover config ) and start it up and then shut it down (my thought was while its starting up/shutting down it creates/saves the one data mover config forced by a 4GB memory allocation). Once the 4GB VM is down reset it to 6 or 8GB again and restart it. Once I did this server_3 was available again ( I've enclosed screen shots again for completeness ). You may notice that I deleted the interfaces in the screen shots, well I repeated the same process after I created the problem using the 8.1.8-37119 OVA file without deleting any of the additional configurations and I received a similar working result.  I don't know if this will help anyone else as this just might be a situation created by my lack of understanding right now but maybe it will help someone. I hope so...  [IMAGE][IMAGE]
[IMAGE][IMAGE]  After what appeared to be a successful failover test I am unable to do anything with server_3.  Is there a way to re-enable the mover, I've rebooted the control station to no avail. I include the following as an aside, I continue to and have always received  messages stating "protocol 0000 is buggy, dev eth0"  Any help would be appreciated
VNX Simulator server_3 is disabled after failover test. Is ther a way to enable 
it?