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

Changing the Disk.MaxLUN parameter on ESXi Hosts (1998)

Last Updated: 6/28/2016Categories: Total Views: 21725Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Details

As per the configuration maximums related to ESXi host storage, the supported SCSI storage devices (LUNs that are presented to ESX host) till vSphere 5.5 is limited to 256 (0 to 255). From vSphere 6.0 onwards the allowed SCSI storage devices count is increased to 1024 (0 to 1023).

ESXi hosts ignore LUNs if the count is exceeding 1024. This limit is controlled by Disk.MaxLUN, which was increased from 256 to 1024 by default in vSphere 6.0.

The value of Disk.MaxLUN also determines how many LUNs the SCSI scan code attempts to discover using individual INQUIRY commands if the SCSI target does not support direct discovery using REPORT_LUNS.

You can modify the Disk.MaxLUN parameter depending on your needs. For example, if your environment has a smaller number of storage devices with LUN IDs from 0 through 100, you can set the parameter to 101 to improve device discovery speed on targets that do not support REPORT_LUNS. In this case, lowering the value can shorten the rescan time and boot time. However, the time to rescan storage devices might depend on other factors, including the type of storage system and the load on the storage system.

Solution

To change the value of Disk.MaxLUN:

Browse to the host in the vSphere Web Client navigator.

Click the Manage tab, and click Settings.

Under System, click Advanced System Settings.

Under Advanced System Settings, select Disk.MaxLUN and click the Edit icon.

Change the existing value to the value of your choice, and click OK.

The value you enter specifies the highest LUN to be recognized and used by the system. For example, to discover and use LUNs from 0 through 100, set Disk.MaxLUN to 101.

Its not recommended to use the "software LUN masking" due to the potential errors. At least be aware that this kind of LUN masking may possibly result in LUN trespassing from the array side with the host.

If the Disk.MaxLUN is reduced from the present value applied to the host then ensure that no LUNs with LU numbers above the specified value are in use by the ESX Server. For this, you need to ensure that you are detaching the LUNs successfully.

For information on unmounting a datastore in ESXi 5.x/6.0, see Unmounting a LUN or detaching a datastore/storage device from multiple VMware ESXi 5.x/6.0 hosts (2004605).

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)

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

Related Versions:

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vCenter Server 6.0.x

VMware vCenter Server 5.5.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