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

Small values are unexpectedly set to traffic shaping settings from Host Client (52076)

Last Updated: 6/20/2018Categories: TroubleshootingTotal Views: 6091Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After enabling traffic shaping from Host Client, Web Client shows about 1-thousandth values in the same settings.

After enabling traffic shaping from Web Client, Host Client shows about 1000-times values in the same settings.

For example, when enabling traffic shaping for a vSwitch from Host Client with default values:

Host Client shows the value as configured:

Average bandwidth : 100000  Kb/s
Peak bandwidth    : 100000  Kb/s
Burst size        : 102400  KB

However Web Client shows 1/1000 or 1/1024 values for each than expected:

Average bandwidth (kbit/s): 100 <--- 1/1000
Peak bandwidth (kbit/s):    100 <--- 1/1000
Burst size (KB):            100 <--- 1/1024

esxcli shows small values as well:

$ esxcli network vswitch standard policy shaping get -v [vSwitch Name]

Enabled: true
Average Bandwidth: 100 Kbps  <--- 1/1000
Peak Bandwidth: 100 Kbps     <--- 1/1000
Burst Size: 800 Kib          <--- 1/1024  Note:Unit is kilobit, not kilobyte

Note: This can lead Host Client's slow response if Traffic shaping is set to vSwitch connected to Management Network or Management Network vmkernel portgroup

Impact / Risks

This issue can cause unexpected network issues such as slow response of Host Client, ESXi host unresponsive from vCenter or slow response of Virtual Machine access.

Resolution

This is fixed in ESXi 6.5 Update 2, available at VMware Downloads.

Workaround

To work around this issue, use Web Client (Flash or HTML5) or esxcli command instead of Host Client when setting Traffic shaping.

Note: when setting Traffic shaping by esxcli, the unit of Burst Size is Kib(kibibit) so you need to multiply the value by 8(byte to bit) than you set from Web Client. For example,

When you set the following settings from Web Client:

Average bandwidth (kbit/s): 100000
Peak bandwidth (kbit/s):    100000
Burst size (KB):            102400

​When you set the traffic shaping from the command line :

when the target is Standard vSwitch:

$ esxcli network vswitch standard policy shaping set --vswitch-name [vSwitch Name] --enabled true --avg-bandwidth 100000 --peak-bandwidth 100000 --burst-size 819200

when the target is Port Group:

$ esxcli network vswitch standard portgroup policy shaping get --portgroup-name [Portgroup Name] --enabled true --avg-bandwidth 100000 --peak-bandwidth 100000 --burst-size 819200

Related Information

Host Client からのトラフィック シェーピングの設定に小さな値が予期せず設定される (52952)
中文简体：源自 Host Client 中的流量调整设置意外地被设置了很小的值

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant