Details
Symptoms
The ESXi/ESX host system fails to report a physical path to storage. The maximum number of supported paths (1024) is reached.
For example, if an ESXi/ESX host does not detect all the paths to the SAN, more than 1024 physical paths might be connected. You see messages similar to:
The maximum number of supported paths of 1024 has been reached. Path vmhba2:C0:T0:L3 could not be added.
The number of paths allocated has reached the maximum: 1024. Path: vmhba5:C0:T6:L28 will not be allocated. This warning won't be repeated until some paths are removed.
Impact
Storage paths that are discovered after the first 1024 are not added to the system. You will not have access to some of the storage paths, and possibly some storage devices, that are configured to be accessible by the system.
Solution
Reconfigure the storage attached to the ESXi/ESX host so that the total number of physical paths to storage is limited to 1024.
For more information about the maximum number of paths supported, see the Configuration Maximums documentation on the VMware web site.
To add more LUNs:
-
Examine the LUNs the host has access to and identify the LUNs that it is not required to see.
-
Unpresent these LUNs.
-
Unmask the LUNs from ESX/ESXi before unpresenting them. For more information, see Masking a LUN from ESX and ESXi using the MASK_PATH plug-in (1009449).
-
Identify whether data on certain LUNs can be consolidated on to one LUN. Ensure that you use Storage vMotion or cold migration to move the data off a LUN if you are planning to consolidate data on to one LUN. You can then unpresent the LUNs from the host whose data has been consolidated. For more information, see Masking a LUN from ESX and ESXi using the MASK_PATH plug-in (1009449).
-
Verify that the number of paths you have per LUN and whether you can reduce the number of paths, making sure that you do not compromise on both the HBA and the switch and controller.
Additional Information
For translated versions of this article, see:
