HostNetworkSystem.UpdateNetworkConfig fail

Ever get this error when you try to migrate a standard switch vmkernel port to a DvS?

"Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-64" on vCenter Server "vCenter.company.com" failed."

It is most likly because the SvS is being used by something. In my case, it was the "Core Dump" feature utilizing the SvS. From the command line, run this to check the configuration: "esxcli system coredump network get". If you get a configuration that is "true", you will need to disable this for now. To issue the disable command: "esxcli system coredump network set –enable false". Check the config again by typing: "esxcli system coredump network get". you should now see the status as "false". Now migrate your interface to the DvS. Once it has been moved, re-enable Core Dump by typing "esxcli system coredump network set –interface-name vmk0 –server-ipv4 10.x.x.x –server-port 6500". Of course the 10.x.x.x should be the vcenter ip and check to make sure what port you are using from your original get command. After this, issue the "esxcli system coredump network get" command one more time to make sure the configuration matches from the previous configuration on the SvS.

Easy as pie – Nexus 1000V Installation Management Center

New to release 4.2(1)SV1(5.1) is the IMC. Forget installing the Nexus 1000v in 7 minutes, the installation management center will get you there in 4 minutes! This GUI makes it super easy to deploy the appliance. Before, you had to deploy an ova, step thru the config wizard and then use a java web page to configure the Nexus. Those steps were still pretty easy. Now with the Installation Management Center you can configure everything in one step!

When you extract the Nexus install from the zip file, there is a "installer_app" directory. In there you will find a Nexus1000v-install.jar file. This launches the Installation Management Center.

Choose where to deploy…

Upload ova and choose redundancy..

After these steps, the Nexus VM or VM's are deployed and configured automatically. 

 

Cisco documentation for the process can be found here.