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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Sample Configuration - ESX/ESXi connecting to physical switch via VLAN access mode and External Switch VLAN Tagging (EST Mode) (1004127)

Last Updated: 3/20/2024Categories: How toTotal Views: 181745Language:
Chinese (Simplified)JapaneseEnglish

40 like this article

Subscribe to get an email
newsletter with new updates

40 people found this helpful Please provide article feedback:

Purpose

This article describes connecting ESXi/ESX to Cisco IOS switches VLAN port.

Resolution

VLAN Access and Layer 2 switching

Physical LAN switch is configured for Virtual LAN (VLAN) segmentation.

ESXi/ESX simply connects to a switch port that belongs to a VLAN at physical switch level.

Cisco defines a VLAN as a broadcast domain within a switched network.

VLANs allow you to segment your switched network so that broadcast domains are smaller, leaving more bandwidth for your end nodes.

Devices that are in one VLAN do not receive broadcasts from devices in another VLAN.

For devices on different VLANs to communicate, a layer 3 device (usually a router) must be used.

VLAN configuration is recommended for securing network traffic.

Virtual Switch (ESX/ESXi) configuration to connect to VLAN switch port

No VLAN configuration is required on ESXi/ESX side.

Set ESX port group to belong to VLAN 0.

Value zero as VLAN means that the vSwitch is not VLAN tagging the ESXi/ESX packets.

Virtual switch NIC teaming policy set to route based on originating virtual port ID by default depending if ether-channel is enabled on switch port.

If Ether-channel is configured on Cisco switch port virtual switch NIC teaming policy is set to route base on IP HASH.

Physical Switch Configuration (Cisco, HP, DELL, etc)

Physical switch Mode Access (Layer2)

Switch port access VLAN tagging (ID)

Define VLAN interface

Assign IP range to VLAN interface

VLAN routing may be required or VLAN Isolation – (refer to VLAN layer 3 routing Article)

These commands are applied on Cisco IOS to configure switch port for VLAN access:

interface GigabitEthernet1/15

switchport ( Configures the LAN port for Layer 2 switching)

switchport access vlan vlan_ID ( The value can be 1 through 4094, except reserved VLANs)
switchport mode access ( Configures the port to be an access port to prevent trunk negotiation delays)

spanning-tree portfast ( Configure port-fast for initial STP delay)

This image is a sample EST topology:

Configuration within the vSphere/VMware Infrastructure Client or vSphere Web Client

To configure this within the vSphere/VMware Infrastructure Client:

Highlight the ESXi/ESX Server host.

Click Configuration > Networking > Properties.

Highlight the virtual switch in the Ports tab.

Click Edit.

Click the General tab.

Type a value of 0 or NONE in the VLAN ID field. This indicates that VLAN Tagging is off.

Click the NIC Teaming tab.

From the Load Balancing dropdown, choose Route based on originating virtual port ID

Verify that there is at least one network adapter listed under ActiveAdapters

To configure within the vSphere Web Client.

In the vSphere Web Client, navigate to the host.

On Manage tab, click Networking

Click Virtual Switches in the left panel and click the virtual switch that requires a change in its load balancing policy.

Click Edit Setting > Teaming and Failover.

From the Load Balancing dropdown, select Route based on originating virtual port ID.

Click OK.

To perform VLAN configuration and verification via the command line:

Run the command:

esxcfg-vswitch –l

The results appear similar to:

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 64 5 64 1500 vmnic3,vmnic1

PortGroup Name VLAN ID Used Ports Uplinks

VM Network 0 0 vmnic1,vmnic3
Service Console 0 1 vmnic1,vmnic3

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch2 64 8 64 1500 vmnic2,vmnic0

PortGroup Name VLAN ID Used Ports Uplinks

VMkernel 0 1 vmnic0,vmnic2

Service Console 2 0 1 vmnic0,vmnic2

Production 0 2 vmnic0,vmnic2

If the VLAN ID is missing or incorrect, correct the VLAN ID value with the command:

esxcfg-vswitch -v VLAN -p “Service Console” vSwitch0

Related Information

STP may cause temporary loss of network connectivity when a failover or failback event occurs
サンプル構成 - VLAN アクセス モードおよび外部スイッチ VLAN タギング（EST モード）を介した ESX/ESXi の物理スイッチへの接続
配置示例 - 通过 VLAN 访问模式和外部交换机 VLAN 标记（EST 模式）将 ESX/ESXi 连接到物理交换机

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 VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

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