Applying host profile to the ESX host fails with error: Operation not supported
book
Article ID: 324299
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
- Applying a host profile to the vSphere ESX host using vCenter Server fails
- You see the error:
Error during the configuration of the host: Operation not supported: Operation not supported
- In the %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Logs\vpxd.log file of vCenter Server, you see entries similar to:
[2010-03-15 07:24:49.098 0x142e6b90 info 'App'] [VpxLRO] -- BEGIN task-32 -- -- vpxapi.VpxaService.applyHostConfig -- 52e0fb5d-####-####-####-########191
[2010-03-15 07:24:49.098 0x142e6b90 verbose 'App'] ApplyHostConfig: applying the config to the host.
[2010-03-15 07:24:49.115 0x142e6b90 verbose 'App'] ApplyHostConfig: Updating the linkSpeed for device vmnic4 [2010-03-15 07:24:49.116 0x146f2b90 verbose 'VpxaHalCnxHostagent'] Received callback in WaitForUpdatesDone [2010-03-15 07:24:49.116 0x146f2b90 verbose 'VpxaHalCnxHostagent'] [VpxaHalCnxHostagent::ProcessUpdate] Applying updates from 17 to 18 (at 17)
[2010-03-15 07:24:49.125 0x14670b90 verbose 'VpxaHalCnxHostagent'] Received callback in WaitForUpdatesDone [2010-03-15 07:24:49.125 0x14670b90 verbose 'VpxaHalCnxHostagent'] [VpxaHalCnxHostagent::ProcessUpdate] Applying updates from 18 to 19 (at 18)
[2010-03-15 07:24:49.126 0x142e6b90 verbose 'PropertyProvider'] RecordOp ASSIGN: info.state, task-32
[2010-03-15 07:24:49.126 0x142e6b90 verbose 'PropertyProvider'] RecordOp ASSIGN: info.cancelable, task-32 [2010-03-15 07:24:49.126 0x142e6b90 verbose 'PropertyProvider'] RecordOp ASSIGN: info.error, task-32
[2010-03-15 07:24:49.126 0x142e6b90 info 'App'] [VpxLRO] -- FINISH task-32 -- -- vpxapi.VpxaService.applyHostConfig -- 52e0fb5d-####-####-####-########191
[2010-03-15 07:24:49.126 0x142e6b90 info 'App'] [VpxLRO] -- ERROR task-32 -- -- vpxapi.VpxaService.applyHostConfig: vim.fault.PlatformConfigFault: (vim.fault.PlatformConfigFault) { dynamicType = <unset>, faultCause = (vmodl.MethodFault) null, text = "Operation not supported: Operation not supported", msg = "Error during the configuration of the host: Operation not supported: Operation not supported",
[2010-03-15 07:24:49.126 0x142e6b90 verbose 'PropertyProvider'] RecordOp ASSIGN: info.completeTime, task-32
- You see the following error in the /var/log/messages:
May 31 18:11:23 Vpxa: [2011-05-31 18:11:23.788 FF91DB10 verbose 'App' opID=########-######85-3c] ApplyHostConfig: Updating the linkSpeed for device vmnic2
May 31 18:11:23 Vpxa: [2011-05-31 18:11:23.789 1AF41B90 verbose 'VpxaHalCnxHostagent'] Received callback in WaitForUpdatesDone
May 31 18:11:23 Vpxa: [2011-05-31 18:11:23.789 1AF41B90 verbose 'VpxaHalCnxHostagent'] [VpxaHalCnxHostagent::ProcessUpdate] Applying updates from 9913 to 9914 (at 9913)
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.789 3D80DB90 info 'TaskManager' opID=########-######85-3c] Task Created: haTask-ha-host-vim.host.NetworkSystem.updatePhysicalNicLinkSpeed-22837
May 31 18:11:23 Vpxa: [2011-05-31 18:11:23.791 1B004B90 verbose 'VpxaHalCnxHostagent'] Received callback in WaitForUpdatesDone
May 31 18:11:23 Vpxa: [2011-05-31 18:11:23.791 1B004B90 verbose 'VpxaHalCnxHostagent'] [VpxaHalCnxHostagent::ProcessUpdate] Applying updates from 9914 to 9915 (at 9914)
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 error 'NetworkProvider' opID=########-######85-3c] DoSetPhysicalNicLinkSpeed: Operation not supported: Operation not supported
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'App' opID=########-######85-3c] AdapterServer caught exception: 3ded0be8
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'TaskManager' opID=########-######85-3c] Task Completed: haTask-ha-host-vim.host.NetworkSystem.updatePhysicalNicLinkSpeed-22837 Status error
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'Vmomi' opID=########-######85-3c] Activation [N5Vmomi10ActivationE:0xfc5f218]: Invoke done [updatePhysicalNicLinkSpeed] on [vim.host.NetworkSystem:networkSystem]
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 verbose 'Vmomi' opID=########-######85-3c] Arg device:
May 31 18:11:23 Hostd: "vmnic2"
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 verbose 'Vmomi' opID=########-######85-3c] Arg linkSpeed:
May 31 18:11:23 Hostd: (null)
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'Vmomi' opID=########-######85-3c] Throw vim.fault.PlatformConfigFault
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'Vmomi' opID=########-######85-3c] Result:
May 31 18:11:23 Hostd: (vim.fault.PlatformConfigFault) {
May 31 18:11:23 Hostd: dynamicType = <unset>,
May 31 18:11:23 Hostd: faultCause = (vmodl.MethodFault) null,
May 31 18:11:23 Hostd: faultMessage = (vmodl.LocalizableMessage) [
May 31 18:11:23 Hostd: (vmodl.LocalizableMessage) {
May 31 18:11:23 Hostd: dynamicType = <unset>,
May 31 18:11:23 Hostd: key = "com.vmware.esx.hostctl.default",
May 31 18:11:23 Hostd: arg = (vmodl.KeyAnyValue) [
May 31 18:11:23 Hostd: (vmodl.KeyAnyValue) {
May 31 18:11:23 Hostd: dynamicType = <unset>,
May 31 18:11:23 Hostd: key = "reason",
May 31 18:11:23 Hostd: value = "Operation not supported: Operation not supported",
May 31 18:11:23 Hostd: }
May 31 18:11:23 Hostd: ],
May 31 18:11:23 Hostd: message = <unset>,
May 31 18:11:23 Hostd: }
May 31 18:11:23 Hostd: ],
May 31 18:11:23 Hostd: text = "",
May 31 18:11:23 Hostd: msg = ""
May 31 18:11:23 Hostd: }
Environment
VMware vCenter Server 4.1.x
VMware vCenter Server 4.0.x
Resolution
This is a known issue and occurs when using 10GB NICs in your ESX configuration.
To work around this issue when using 10GB vmnics that are not physically patched or cabled:
- Right click the host profile and click Edit Profile.
- Click + to expand the profile.
- Click Networking Configuration.
- Click Edit to the right of Which physical NICs should be connected to this vSwitch?.
- Click the vmnic in the Names of the Nics to attach field.
- Click Delete.
- Click OK.
To work around this issue when using other 10GB vmnics:
- Right click the host profile and click Edit Profile.
- Click + to expand the profile.
- Click Physical NIC configuration.
- Click Physical network adapter and ensure that the Physical NIC to configure is the vmnic found in the logs.
- Click Edit to the right of How should the physical NIC be configured?.
- Select fixed physical nic configuration from the dropdown.
- Enter the name of physical nic in the *Name of the physical NIC to configure field.
- Enter the link speed in the *Link speed in Mbps field.
- Select the *Flag indicating if the NIC should be duplex check box.
- Click OK.
This changes the policy from auto-negotiate to a fixed setting and allows the the host profile to be successfully applied.
Feedback
thumb_up
Yes
thumb_down
No