Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

vSAN -- Health Service -- Proactive Tests -- Network Performance Test (58895)

Last Updated: 7/4/2023Categories: InformationalTotal Views: 14411Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

This article explains the Proactive Test "Network performance test" in vSAN (formerly known as "Multicast performance test" in releases before vSphere 6.5 P02) and provides details on why it might report an error.

The Network performance test can be used to assess if there are any connectivity issues in the network used by vSAN. In addition, the result can be used as a reference to check if the network speed among the hosts meets the hardware specification and is sufficient to support the workloads hosted on vSAN.

In a regular or stretched cluster configuration, the test is performed between the hosts in the cluster. However, if HCIMesh is in use and the test is triggered on the client cluster, it will verify the network bandwidth between the hosts in the client cluster and the hosts in the server cluster separately.

During the test, all connected hosts are organized to form a circular list, and every host will be sending network packets to the next host while receiving packets from the previous host at the same time. Upon the completion of the test, the actual network bandwidth of each link between the sender host and the receiver host is reported.

testID: com.vmware.vsan.health.test.networkperftest

To access this proactive network performance test, go to: Web Client --> Select your vSAN Cluster --> Monitor Tab --> vSAN --> Proactive Tests

This test is part of vSAN’s proactive tests, for more information, please check Proactive Test document.

Solution

Q: How to determine if there are network connectivity issues?
A: There are 2 things to be considered when interpreting the test result:
1) does the result meet the hardware specification?
2) is the network speed sufficient to support the workloads hosted on vSAN?

vSAN requires a minimum NIC speed of 1Gbps per host, and vSAN ESA requires a minimum aggregated NIC speed of 25Gbps per host. The bandwidth required for vSAN is decided by the workloads hosted on vSAN, and in general more bandwidth is required to support more vSAN workloads. Both the result state and the result value shall be used to determine if the network connection is at a healthy state. Take an example, a vSAN cluster configured 10Gbps for vSAN on each host, the result state shows all green and the result value is somewhere around 5Gbps, even though the test state doesn’t report any error, but there could still be network issues in the cluster as the test cannot achieve a result close to 10Gbps.

The test will show a resulting state:

For vSAN:

Red if the speed is 0 Mb/s

Yellow if the speed is less than 850 Mb/s

Green if the speed is greater than or equal to 850 Mb/s

For vSAN ESA

Red if the speed is 0 Mb/s

Blue if the speed is greater than 0 Mb/s

Note: Any network connection that fails to meet the hardware specification should be checked to ensure the network bandwidth will not affect vSAN performance.

Q: How to troubleshoot and fix the network connectivity issues?
A: Below is a list of the most commonly seen errors that could cause network connectivity issues.

Uncertified or outdated NIC driver/firmware

Incorrect network connection/cabling for NIC, switch port, etc

Incorrect virtual switch/port group/VLAN setting

Incorrect MTU setting on the physical switch, DVS or vmk

Improper TCP ring size setting

Malfunctioning hardware or not certified switch vendor cable choice

Insufficient physical switch/port buffer

Over-committed or insufficient designed ISL between switch/switch layers

Note: in case you have difficulty identifying the root cause of the problem please reach out to your field support for troubleshooting assistance.

Q: How to design the network to achieve the best performance of vSAN?
A: Please go to vSAN Network Design guide for guidance.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 8.0.x

VMware vSAN 7.0.x

VMware vSAN 6.7.x

Take Our Survey

Support Assistant