"A specified parameter was not correct" error when modifying networking

[VMmatty]

I've got 5 identical ESX hosts that I just built. I'm not sure what has changed on one of them, but I can no longer modify network settings. If I try to add a port group, link a NIC, or almost anything else I get "A specified parameter was not correct." The behavior persists through a reboot,

Any thoughts?

[VMmatty]

I ended up resolving this myself. In case anyone else has a similar issue, check the hostd.log file. I did "tail -f hostd.log" and then tried to add some networking and saw that it was still looking for a pNIC I had unlinked before it was cabled correctly. For some reason it was still looking for that NIC and was throwing an error.

I was able to link the NIC back via the cmdline and now I can modify networking without an issue. Hope this helps someone else at some point.

[whinshaw]

Are you working with a distributed switch or a regular vSwitch?

Have you tried to manually add them through console instead of using vCenter's GUI?

If you find this information useful, please award points for

"correct"

or "helpful".

Wes Hinshaw

www.myvmland.com

[whinshaw]

ah, you beat me to it.

If you find this information useful, please award points for

"correct"

or "helpful".

Wes Hinshaw

www.myvmland.com

[cougar694u]

For what it's worth, I had this exact same problem on an ESXi host. Looking at host.d didn't really give me much info, though. I have 8 nics, 1 of which was on a Nexus1000v. I couldn't uplink any other nics, regardless of uplink group (have three).

I had to disconnect host in vCenter, remove from Nexus1000v, restore standard vSwitch, bring back in to vCenter, then migrate back to Nexus1000v. Once I did that, I was able to uplink all 8 nics to the different uplink port groups without issue.

Just an fyi...

~Luke

[SteveAntle]

Hello,

I am experiencing the same issue you had with an ESXi v4.0 host. When I attempt to add a free PHY NIC to a distributed virtual switch I get the error "A specified parameter was not correct.". This error is also persistent across a reboot. I created a standard virtual switch and added the PHY NIC to it successfully. Then I attempted to migrate that PHY NIC to the problematic distributed virtual switch but I get the same error. Any suggestions?

Thanks in advance,

Steve A