Vmotion failing

[sushil]

Hi,

I need help on vmotion configuration.

Due to power outage our cluster went down.

Once it came back our vmotion is failing.

Mac-Pinning we are using with 4 NIC.

TO cross verify it i also tried adding vmotion vlan as system vlan on uplink profile.

But i am not able to remove this system vlan from uplink port-profile.

I wanted to restore my vmotion.

Regards,

Sushil

[Robert Burns]

Sushil,

Can you ping the Vmotion vmk IP from one host to the other?

1. From the CLI of the ESXi host, issue "vmkping 192.168.x.x".  If you can't ping it then you might want to try and create an SVI (VLAN IP address) on your upstream switch and see if you can ping that.  If that still fails we'll look further.

2.  Ensure the VMotion VLAN is created and allowed on the 1000v and upstream switch.

Regards,

Robert

[sushil]

Robert,

vmkping is not responding.

Please do let me know the next step.

Reg,

Sushil

[sushil]

Robert,

My vlan management and data is running on 192.168.10.0/24.

Now added a SVI on upstream that is 192.168.100.254.vmkping responded.

on each 1000v created added ip address 192.168.100.79 and 192.168.100.80 with gateway 192.168.100.254.

It responded.

vmotion successful.

DO i need to create SVI for FT too?

say with 192.168.200.254?

Do i need to add that on uplink port as system vlan 200?

For your information I added system vlan 100 on my uplink profile too.

It is not allowing me to remove from there.

Is it correct if i add vlan 100 and 200 as system vlan on uplink or need to remove those

It is not allowing me to removing vlan 100 as system vlan as it is in use.

Please help.

Regards,

Sushil

[Robert Burns]

Sounds like you were missing the vmk interface on the N1K.

The best practice is to have FT on it's only VLAN (Ex. 200) but I've seen customers use both FT & VMotion on the same VLAN.  If you plan on using FT heavily, then I would setup a new VLAN for this purpose.

FT and VMotion port profiles do NOT need to be system vlans.  Once a system vlan has been added to an uplink port profile it can't be removed.  The only option to remove it is to create a copy of the Uplink Port profile, omitting the VMotion VLAN, and then migrating each adaptor from the old to new Uplink profile.

Regards

Robert

[sushil]

Robert,

I have removed vmotion profile now.

Created replica of uplink port profile as sys-uplink now without vlan 100 in system vlan.

went in Host>Networking>N1k and did manage host.

Picked up both the hosts and then added each nic to new sys-uplink.

Now comes vmk0 window which is my service-console.

What should I do here..

Options are attached.Whcih option to pick so that io am not thrown out of it.

Regards,

Sushil

[Robert Burns]

Once your uplinks are moved you're done. You don't need to do anything with the vmk interface, assuming it's already sitting on the N1K and not a vSwitch.  The system will choose the uplinks to use for each vmk interface, you don't have to do anyting in this regard.  Since you only have one uplink port profile being used called sys-uplink, the vmk interface will use this uplink profile by default.

Robert

[sushil]

Robert,

you mean do not migrate option i need to go.

Is that correct?

Reg,

Sushil

[Robert Burns · Accepted solution]

Correct don't migrate anything.

Robert

[sushil]

It worked Robert.

Removed the old port-profile by first removing system vlan and port channel there and then no port-profile.

All working fine for me.

Thanks again.

Just curious to know why added SVI to resolve FT and Vmotion.

Regards,

Sushil

[Robert Burns]

If the Vmotion VLAN was indeed created on the upstream Switch, in theory it should have worked.  Created an SVI doesn't do anything magic....

Robert

[sushil]

Creating SVI is also not a bad design what do you say?

Sincere thanks to you.

Regards,

Sushil

[Robert Burns]

SVI's are typically for routing.  VMotion requires Layer2 adjacency (non routed). 

I do find it useful for testing as you have found out though ;-)

Rob