Flex 10 and ESX vmotion

[Funtoosh]

We are trying to configure vmotion by using uplink VC Flex 10 module.
We have configured on upllink as vmotion and marked it as private. This we are trying so that we dont go out VC domain and my external Nexus are less utilized. Is it correct assumption or it is not possible ?

I have attached my VC screen shot and also I have created nic profile and created vmkernal seperately as shown .

When I looked my VM log it says



Feb 24 05:17:20.965: vmx| Received migrate 'to' request for mid id 1267006674790479, src ip <10.1.160.20>, dst ip <10
.1.160.10>.
Feb 24 05:17:21.101: vmx| MigrateSetInfo: state=1 srcIp=<10.1.160.20> dstIp=<10.1.160.10> mid=1267006674790479 uuid=3
5303738-3634-5553-4530-303558365731 priority=high
Feb 24 05:17:21.101: vmx| MigrateStateUpdate: Transitioning from state 0 to 1.
Feb 24 05:17:26.496: vmx| VMXVmdbCbVmVmxMigrate: Got SET callback for /vm/#_VMX/vmx/migrateState/cmd/##1_38/op/=start
Feb 24 05:17:26.496: vmx| VmxMigrateGetStartParam: mid=48055fac7684f dstwid=1090
Feb 24 05:17:26.496: vmx| Received migrate 'start' request for mig id 1267006674790479, dest world id 1090.
Feb 24 05:17:26.497: vmx| MigrateStateUpdate: Transitioning from state 1 to 2.
Feb 24 05:18:41.498: vcpu-0| MigrateStatusFailure: switching to new log file.
Feb 24 05:18:41.509: vcpu-0| MigrateStatusFailure: Now in new log file.
Feb 24 05:18:41.522: vcpu-0| MigrateStatusFailure: Migration failed while copying data. Timeout.
Feb 24 05:18:41.522: vcpu-0|
Feb 24 05:18:41.523: vcpu-0| MigrateSetInfo: state=5 srcIp=<0.0.0.0> dstIp=<0.0.0.0> mid=0 uuid=(null) priority=(null
)
Feb 24 05:18:41.523: vcpu-0| MigrateStateUpdate: Transitioning from state 2 to 5.
Feb 24 05:18:41.523: vcpu-0| Migrate_ClearDoneState: cleared state. State was 5.
Feb 24 05:18:41.523: vcpu-0| MigrateStateUpdate: Transitioning from state 5 to 0.
Feb 24 05:18:41.523: vcpu-0| Msg_Post: Error
Feb 24 05:18:41.523: vcpu-0| [msg.checkpoint.precopyfailure] Migration to host <10.1.160.10> failed with error Timeou
t (0xbad0020)
Feb 24 05:18:41.523: vcpu-0| ----------------------------------------

[Funtoosh]

One more screen shot

[Adrian Clint]

Vikash - DISABLE Private

If you enable it then all communication must go out of the domain and be switched.

Its the inverse of what you think.

PRIVATE is not a private network within the VC. It means that port traffic on this VC network is Private from all other ports. Not what you want on a Vmotion network.

[Funtoosh]

I got it tested and it worked fine. Thanks for your suggestion. Still I did not got my answer is there a way that vmotion traffic does not hit external switch.

How if I setup two chassis of C7000? Do I still have to go to my external Nexus?

[The Brit · Accepted solution]

Try this.

Create a VC Ethernet network (VC vLan), however do not assign it any uplink ports.

Assign this network to the blade port that you wish to use for vmotion. This should restrict traffic to be only between blades which have a NIC assigned to this network.

Note that this is exclusive, i.e. it will not be possible for traffic on this VC network to leave the enclosure (because there are no uplink assigned to it)

Note also that this approach is used for "heartbeat" communications between clustered blades.

HTH

Dave.

[WFHC-WI]

Hi Vikash,

If you want to vMotion across two enclosures you can link your Virtual Connect modules together. Use the CX4 connector on the far left side of each module for this link. You should also link the two enclosures together using a normal CAT5/6/6e cable connected to the port between the Onboard Administrators.

You can now have an internal network spanning two enclosures that never touches your Nexus switch.

good luck, we appreciate points if these responses helped!

[Funtoosh]

Dave that is exactly what I was looking . Thanks I have awarded you point.

[Funtoosh]

Watch out my blog and its dedicated to Dave.
vikashkumarroy.blogspot.com