Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Applying host profile to the ESX host fails with error: Operation not supported (1019659)

Last Updated: 8/6/2020Categories: TroubleshootingTotal Views: 7712Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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-246a-0f78-1ab4-38bed12b0191
[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-246a-0f78-1ab4-38bed12b0191
[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=9220746D-00000385-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=9220746D-00000385-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=9220746D-00000385-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=9220746D-00000385-3c] AdapterServer caught exception: 3ded0be8
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'TaskManager' opID=9220746D-00000385-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=9220746D-00000385-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=9220746D-00000385-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=9220746D-00000385-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=9220746D-00000385-3c] Throw vim.fault.PlatformConfigFault
May 31 18:11:23 Hostd: [2011-05-31 18:11:23.811 3D8D0B90 info 'Vmomi' opID=9220746D-00000385-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: }

Resolution

This is a known issue and occurs when using 10GB NICs in your ESX configuration.

To workaround 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 workaround 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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Workspace One UEM - 古いデバイス レコードを削除できない (80230)

KB
•
AAGNT-188391：企業情報リセットにより、Zebra Android 10 で Workspace ONE Intelligent Hub が加入解除される (80224)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant