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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Configuring Network Switches for VLAN Tagging (1266)

Last Updated: 5/12/2015Categories: InformationalTotal Views: 15237Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

Why is VLAN not working on my system?

Solution

If you use ESX Server to route VLAN network traffic, you may need to reconfigure switches attached to your system. Some switches define a "native" VLAN that is used by default. A native VLAN is associated with a particular VLAN ID number. For instance, on a Cisco switch the ID of the native VLAN is 1, by default. Network traffic using the same ID number as a native VLAN may have have the VLAN ID (802.1q) tags automatically removed when routed through the switch, depending on how the switch is configured.
ESX Server requires these ID tags to route traffic in the two VLAN modes supported within the system:

Virtual switch routing with port groups (switch tagging)

Virtual machine routing (guest tagging)

Check the configuration of attached switches to ensure that default settings do not interfere with the VLAN modes you have chosen for your server. Switch ports connected to your system must be configured as trunk ports that pass through traffic without removing VLAN ID tags.
You should avoid using a native VLAN when designing the configuration for your external and virtual switches. Using specific ID tags, rather than the default VLAN ID, may prevent networking failures if an external switch is returned to its default settings. Also, avoiding native VLANs provides a more secure interface between virtual machines and your network.

If you are already using a native VLAN, you can reconfigure your switch to pass through ID tags on all ports, including native traffic (that is, messages using the ID of the native VLAN). Set the switch to enable 802.1q tags for all VLAN ID values, either globally or for the trunk ports connected to your system. See the documentation for your switch for details.

For more information about VLANs and ESXi/ESX Servers, see the VLAN Configuration section in the vSphere Networking guide.

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
•
仮想 NIC の静的 MAC アドレスを設定する (219)

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 vSphere ESXi

VMware ESX Server

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant