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

Restarting the software iSCSI stack (1004033)

Last Updated: 3/20/2024Categories: Total Views: 27154Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Storage disappeared unexpectedly.

Storage is missing after a reboot of the ESX host.

Change to the initiator name (IQN) does not appear to have been accepted.

Purpose

This document discusses problems with the software iSCSI stack that can be resolved by restarting the stack instead of rebooting the entire ESX system.

This may be necessary when the detection of storage at boot time fails to acquire the iSCSI targets from the array or when the iSCSI stack stops responding.

Resolution

Caution: This procedure disables all iSCSI traffic that uses the software initiator. Prior to performing these steps:

Ensure that there are no virtual machines running on a datastore located on the iSCSI LUNs on the host.

Ensure that there are no 3rd party scripts or utilities running on service console which could access iSCSI LUNs on the host. The lsof utility can be used to identify any processes with open file locks to files residing on Datastores on iSCSI LUNs. For more information on starting and stopping 3rd party services or scripts, please engage the appropriate 3rd party software vendor.

To restart the software iSCSI stack:

Disable the software iSCSI configuration with the command:

esxcfg-swiscsi -d

Terminate the software iSCSI processes with the command:

esxcfg-swiscsi -k

In some cases, the iSCSI stack is in an unresponsive state and does not terminate on this command. If this happens, you must find the process ID and issue a terminate command directly to the operating system for this process.

Obtain the process ID for the vmkiscsi processes with the command:

ps ax | grep vmkiscsid

Terminate the process with the command:

kill <process ID>

Enable the software iSCSI configuration with the command:

esxcfg-swiscsi -e

Perform a rescan of the software initiator with the command:

esxcfg-rescan vmhba40

Note: This procedure only applies if you are using the software iSCSI initiator.

Memory resource starvation is one possible reason for the iSCSI stack to become unresponsive. This can occur if agents have been installed on the service console. It is advisable to increase the amount of memory assigned to the service console. For more information, see Increasing the amount of RAM assigned to the ESX Server service console (1003501).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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 ESX Server

Related Versions:

VMware ESX Server 3.0.x

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