1. That really is an issue you'd need to check on the client, to see where it is getting the "wrong" IP from. As stated perhaps something was cached, or wasn't using the local hosts file as expected. 2. Yes, that is how it is designed and how it works, but don't forget it's not really that simple. You need to make sure everything is setup correctly on the secondary cluster (smartconnect, shares) and in an actual failover you will want to make sure you block access to the primary cluster shares before doing a final sync to make sure you don't lose anything, before following the failover process.