Clik here to view.
Re: Failed to add vmkernel nic: A specified parameter was not correct.
You need to specify the portgroup in which the new VMkernel interface will connect to, if you haven't created the portgroup, then you need to create it first. Try this: [vi-admin@scofield profile]$...
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct.
It's work fine.But I told about distributed vSwitch.
View ArticleClik here to view.
Re: Failed to add vmkernel nic: A specified parameter was not correct.
You should take a look at Scott Lowe's post about dvs + Jumbo Frames: http://blog.scottlowe.org/2009/05/21/vmware-vsphere-vds-vmkernel-ports-and-jumbo-frames/ There's a few things you need to do to get...
View ArticleClik here to view.
Re: Failed to add vmkernel nic: A specified parameter was not correct.
Ok, thank you. I found interesting thing. Look: All work fine in ssh to ESX. Second: when I try to repeat this on ESXi with vSphere CLI (on screenshot you see ssh to vMA) I have an error.
View ArticleFailed to add vmkernel nic: A specified parameter was not correct. vSphere...
Hi. I try to add vmknic with Jumbo Frames to my distributed virtual switch. I read the guide vSphere Command-Line Interface Installation and Reference Guide:"vicfg-vmknic -a -i DHCP "vmk5"I see error...
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct.
I am having the same problem with ESXi and the CLI and receiving the same error (cannot specify dvsName or dvPortID). If it matters I am using the Nexus 1000V, not the native distributed virtual...
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct.
OK! I figured out a workaround. Since adding a vmkernel interface remotely doesn't seem to work with DVS, I simply created one on a standard vSwitch and then migrated it to the DVS. And voila: the MTU...
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct.
Did you ever get this to work? I am running into the exact same error on ESXi as you did. However, I cannot find anyone who has fixed that error. If you did, could you let me know please...?
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct.
As far as I know, the only fix is the workaround I detail above. It works with ESXi fine.
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct.
Another workaround that always work is both remove and add the vmkX in unsupported mode.
View ArticleRe: Failed to add vmkernel nic: A specified parameter was not correct....
Hello. Is there any way to do this through the Gui.I have 2 hosts each with 2 nics. The second host this worked fine but I am unable to do so on the first hostI did it the same way on both and i get...
View ArticleClik here to view.
Re: Failed to add vmkernel nic: A specified parameter was not correct....
The workaround mentioned above is what worked for me:Add a port group to a regular vSwitch: esxcfg-vswitch -A "iSCSI3" vSwitch1add the new vmkernel nic to this portgroup: esxcfg-vmknic -a -i DHCP -p...
View Article