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

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

ESX/ESXi power on error: Unable to set VMkernel gateway as there are no VMkernel interfaces on the same network (1002662)

Last Updated: 9/3/2014Categories: TroubleshootingTotal Views: 93460Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

When an ESX/ESXi host is powered on, the following error message appears during startup process:

Unable to set VMkernel gateway as there are no VMkernel interfaces on the same network

Solution

VMkernel interfaces are used by ESX/ESXi host's internal TCP/IP stack for three purposes:

To facilitate VMotion between ESX hosts

To connect to iSCSI storage arrays (IP SAN)

To connect to NFS storage servers (NAS)

Like a traditional TCP/IP stack, the VMkernel TCP/IP stack provides the ability to route IP datagrams to remote subnets. Although VMware does not recommend that VMotion traffic be routed, both iSCSI and NFS traffic may be routed through a gateway to reach a storage server on a different subnet.

This routing gateway, called the VMkernel gateway, is the IP address of a router or Layer 3 switch on the same subnet as the VMkernel interface itself. This router (or L3 switch) is then responsible for forwarding the VMkernel's IP datagrams in the direction of the destination subnet.

If a VMkernel gateway is specified with an IP address that does not exist within any of the defined VMkernel interfaces' subnets, the Unable to set VMkernel gateway error message appears on system startup. For example, consider the following output:

[root@ESX1 root]# esxcfg-vmknic -l
Port Group IP Address Netmask Broadcast MAC Address MTU Enabled
iSCSI_SAN 192.168.1.100 255.255.255.0 192.168.1.255 MAC_Address1 1514 true
VMotion 192.168.2.100 255.255.255.0 192.168.2.255 MAC_Address2 1514 true

The esxcfg-vmknic -l command provides a listing of all VMkernel interfaces defined on an ESX host. In the example above, there are two VMkernel interfaces:

iSCSI_SAN on network 192.168.1.0/24

VMotion on network 192.168.2.0/24

However, if we verify the IP address that has been assigned to the VMkernel gateway address, we discover an issue:

[root@ESX1 root]# esxcfg-route -l

VM Kernel Routes:
Network Netmask Gateway
192.168.1.0 255.255.255.0 Local Subnet
192.168.2.0 255.255.255.0 Local Subnet
default 0.0.0.0 192.168.0.254

The esxcfg-route -l command provides a listing of all routing table entries within the VMkernel TCP/IP stack. In the example above, the default entry (which corresponds to the VMkernel gateway address) shows a gateway address of 192.168.0.254. Because 192.168.0.254 exists on the 192.168.0.0/24 network and we have no VMkernel interfaces defined on this network, ESX host considers this a misconfiguration and produces the Unable to set VMkernel gateway as there are not VMkernel interfaces on the same network error on startup.

This error message can be safely ignored if routing is not required on the various VMkernel interfaces. However, if a VMkernel gateway is required in order to reach a remote iSCSI or NFS storage server, it must be configured and valid.

The VMkernel gateway is easily configured as follows:

Using VMware Infrastructure (VI) Client, connect to the ESX host you wish to modify. Alternatively, you may connect to the VirtualCenter server that manages this ESX host.

Select the ESX host in the inventory, and click the Configuration tab.

Under the Hardware list, select Networking.

Identify the vSwitch that contains the VMkernel interface to be modified and click Properties.

In the vSwitch Properties window, select the appropriate VMkernel interface and click Edit.

In the Properties window for the VMkernel interface, click Edit next to "VMkernel Default Gateway".

In the DNS and Routing Configuration window, specify the correct default gateway address.

Click OK to commit the VMkernel default gateway.

Click OK to commit the VMkernel interface changes.

Click Close to close the vSwitch Properties window.

At this point, the VMkernel default gateway is set appropriately and the error message during startup no longer appears. If you are unable to rename the VMkernel port, see Unable to rename or delete a VMkernel Portgroup after upgrading to ESX 3.5 (1003933).

To configure the VMkernel gateway using the command line:

To see the default gateway of VMkernel, run the command:

# esxcfg-route

To set the default gateway of VMkernel, run the command:

# esxcfg-route <IP address>

To add a route to the VMkernel, run the command:

esxcfg-route -a [<network> <gateway>] | <default gateway>

For example:

To add a route to 192.168.100.0 network through 192.168.0.1, run the command:

esxcfg-route -a 192.168.100.0/24 192.168.0.1

Or

esxcfg-route -a 192.168.100.0 255.255.255.0 192.168.0.1

To set the VMkernel default gateway to 192.168.0.1, run the command:

esxcfg-route 192.168.0.1

Or

esxcfg-route -a default 192.168.0.1

Note: You can specify additional IP and subnet for the VMkernel adapter, but there can only be one default gateway.

For more information, see Tech Support Mode for Emergency Support (1003677).
For more information on ESXi 5.1 and ESXi 5.5, see Configuring static routes for vmkernel ports on an ESXi host (2001426).

Additional Information
For translated versions of this article, see:

Español:

Português:

日本語: ESX パワーオン エラー：同じネットワークに VMkernel インターフェイスがないため VMkernel ゲートウェイを設定できない (2078908)

简体中文: ESX 打开电源错误：无法设置 VMkernel 网关，因为同一网络中没有 VMkernel 接口 (2062173)

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.0

VMware VirtualCenter 2.5.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 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