During one of my Storage vMotion tests, there were flashing lights on the front door 100 Mbps switch, and no flashing lights on the back door Gig-e. This signaled that the Storage vMotion operation was actually being performed on the slow network. Also, the progress was slow.
First change was to disconnect Uber's front door vNIC (100Mbps). Also, made sure that the source host (local disk on westwood) and the destination host (shared iSCSI LUN served from Uber on cresskill) had vMotion-enabled vmkernel ports on the same dvSwitch port group.
Once the migration was restarted, the stats were showing 30Mbps network throughput outbound (local-to-shared) and closer to 50Mbps inbound. More testing of the network configuration is needed to verify why vMotion defaulted to the slow network.
No comments:
Post a Comment