Yes, I see now... the problem with our environment is that the two SANs are not on the same storage subnet. Even the vlan tagging is different. We've been doing major upgrades to infrastructure and have created new subnets and vlans... during the process, the different vSphere environments were configured with different storage IPs. Only the virtual machine port group and the vmotion vmkernal port group are the same. The thinking was we would migrate all VMs using vmotion and just schedule downtime. Now that has changed.... I'm still working on a solution to remedy this.
↧