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

TCP Offload features on all Mellanox NICs must be disabled before installing vCenter Server Heartbeat (1024066)

Last Updated: 3/20/2024Categories: How toTotal Views: 33145Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After installing vCenter Server Heartbeat on a server with TCP Offload Engine (TOE) enabled Mellanox NICs, you may experience these symptoms:

Operating system failure (blue screen error)

Packet filter installs but cannot filter traffic

Packet filter installs but the server is not visible on the network

Resolution

vCenter Server Heartbeat is incompatible with TOE, a common feature of 10GB Ethernet cards.

Some newer models of Ethernet cards offer a TOE to help manage TCP/IP communications. vCenter Server Heartbeat is intended to manage the passing or filtering of selected IP addresses, therefore the TOE function must be disabled to allow vCenter Server Heartbeat to exercise intelligent control of TCP/IP communications, depending on whether the server is the active or passive server.

Prior to installing vCenter Server Heartbeat, you must disable these TOE features on all NICs:

Offload IP Security

Offload TCP Segmentation

Offload TCP/IP Checksum

To disable these features:

Locate these features on the Advanced tab of the NIC Properties dialog (Computer Management > Device Manager > Network Adapters). Depending on the NIC and driver combination, the features may be called by slightly different names than those listed above. Consult the NIC documentation before making any changes.

Uninstall the Packet Filter

Stop the vCenter Server Heartbeat service and set NFserverR2 service to manual for the duration of this procedure.

(Skip to step c if the server does not use teamed NICs.) Dissolve any existing NIC team using the vendor-supplied software.

If uninstalling on a Passive server, disconnect the Public Network Cable.

From a command prompt change the directory to C:\VMware\vCenter Server Heartbeat\r2\bin.

Run the command:

nfpktfltr uninstall "\VMware\vCenter Server Heartbeat\r2\drivers\nfpktfltr\"

Delete C:\winnt\system32\drivers\nfpktfltr.sys.

Delete C:\winnt\nfpktfltr*.

Verify that these key(s) have been removed:

Open Regedt32.

Go to HKLM\SYSTEM\CurrentControlSet\Enum\Root\nfpktfltr_mp (highlight nfpktfltr_mp if it exists) and select Security from the menu.

Assign Full Access to the Everyone and System groups (if not already assigned). If there are any other groups without Full Access, assign them the same access as well.

Delete this key.

Follow steps a-d above for CurrentControlSet1 and CurrentControlSet2 as required. The Miniport should be in the same location in the subfolders.

Follow same procedure for HKLM\SYSTEM\CurrentControlSet\Services\nfpkfltr adding 'Full Control' where required to remove the keys completely.

To confirm they have been removed, open Device Manager and select Show Hidden Devices. They should all be gone completely.

Restart the server before re-installing and verify the keys have been removed from Device Manager.

Install the Packet Filter:

Stop the vCenter Server Heartbeat services and set NFserverR2 service to manual for the duration of this procedure.

From a command prompt change the directory to C:\VMware\vCenter Server Heartbeat\r2\bin.

Run the command:

nfpktfltr install "\VMware\vCenter Server Heartbeat\r2\drivers\nfpktfltr\"

Select Yes to all the unsigned driver windows. (You may or may not see these).

Deselect the checkbox for the filter from the VMware Channel NICs.

(Skip this step if the server does not use teamed NICs.) Recreate the teamed NICs using the vendor-supplied software.

Restart the server after installing the drivers.

When the server has restarted, check the packet filter configuration with the commands getfilter and getstate (the servers should respond with PassThru on the active server and Filter on the passive server) and getloadstate (the servers should respond with Filter on both the active and passive servers).

Note: The getloadstate command is only available in vCenter Server Heartbeat 6.3 and later.

Reconnect Public Network Cable if installing on passive server.

Set the NFserverR2 service to automatic again and start vCenter Server Heartbeat.

If required, perform a series of test switches Primary to Secondary and then Secondary to Primary again. This will prove the packet filter is installed and operational.

Uncheck the Packet Filter from the Channel NICs

TCP Offload can be enabled on the Channel NICs but must not be enabled on the Public NIC.

Related Information

vCSHB-Ref-1919
vCenter Server Heartbeat をインストールする前にすべての NIC で TCP オフロード機能を無効にする必要がある

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
升级后执行 vMotion 期间出现错误“无法添加内存页 (Failed to add memory page)” (2143943)

KB
•
如何在 Customer Connect 中邀请用户加入帐户 (2070555)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant