migrating from old vc to new vc

[KNardi]

We recenlty built a VC 2.x license/VC server

I added 2 servers from my old 1.4.x server to the new VC2.0.x server and tried to vmotion I get this error.

"Unable to migrate from xxxxx to xxxxxx Currently connected network interface 'NIC 1' uses network 'CorpNet', which is configured for different offload or security policies on the destination host than on the source host."

These 2 VM's had no issue using vmotion with the 1.4.x VC.

I am running 2.5.x on both VM's.

I thought the new VC2.x was backwards comaptible. Is this true.

Any help is appreciated.

thanks

[boydd]

VC 2.x should be able to do this for you. Quickly verify that the vmotion vswitches are correct.

DB

[KNardi]

The switches are ok. They are on different outbound adapters.

This setup worked fine in the old VC 1.4.x

All I did was remove from the VC 1.4.x to VC 2.0.x

[waynegrow]

Sounds like the security set on the vSwitch on each server is different. Maybe look to see if settings under the Security tab are different.

[KNardi]

Is this something that is set on VC 2.0.x???

I don't see a security setting for the current switch.

[KNardi]

My current ESX security setting is "Medium"

These servers worked with VMOTION before I moved to VC 2.0.x

[waynegrow]

In the VI Client highligt the ESX server and go to the Configuration Tab. Click on Networking and go to the Prperties of the vSwitch. Under the Ports Tab, Edit the proprties of the vSwitch. You will see the Security tab.

[KNardi]

Uh....I don't have a configuration tab?

[encode]

I am also having the same issue. There is no configuration tab, since these are ESX 2.5.x hosts, and the configuration tab is only present for VI 3.

[itsfja]

We are also receiving the same message. There is wide variation as to which hosts will not be allowed to be moved to although they are consistent per guest. Also the message can come up as either warning or error, again consistent per guest.

Regards,

Francis.

[LarsLiljeroth]

I am seeing the same behavior after i upgrade to vc 2.01 patch 2. Any solution to it yet?

/Lars