Many are able to map up to 256 (0 to 255) per . However, the hosts listed in the following table have the following restrictions. (You can indicate the operating system of a particular host by specifying a when defining the associated with a host.)
Important: If you try to map a to a LUN that exceeds the restriction on these operating systems, the host is unable to access the virtual disk.
Operating System
Maximum Number of Mappings*
Solaris with
32
NetWare 5.1
31
HP-UX 11.0
32
HP-UX 11.11
127
Windows 2000
64
Red Hat Linux
128
*The maximum number of mappings differs because of any number of environmental factors. Operating system variables, failover driver issues, and potential data problems influence the number of mappings available.
Consider the following items when working with host types with LUN mapping restrictions:
You cannot change an HBA host port to a restricted host type if there are already virtual disk-to-LUN mappings in the partition that would exceed the limit imposed by the restricted host type.
If the has access to LUNs up to 256 (0 to 255) and a restricted host type is added to the Default Group, the host associated with the restricted host type is able to only access virtual disks in the Default Group with LUNs within its limits. For example, if the Default Group had two virtual disks mapped to LUNs 254 and 255, the host with the restricted host type would not be able to access those two virtual disks.
If the Default Group has a restricted host type assigned and the storage partitions are disabled, only a total of 32 LUNs can be mapped. Any additional virtual disks created are put in the Unidentified Mappings area. If additional mappings are defined for one of these Unidentified Mappings, the Define Additional Mapping dialog shows the LUN list and the Add button as unavailable.
Do not configure dual virtual disk-to-LUN mappings on a Windows host.
If there is a host with a restricted host type that is part of a specific storage partition, all hosts in that partition are limited to the maximum LUNs allowed by the restricted host type.
You cannot move a host with a restricted host type into a partition that already has LUNs mapped that are greater than what is allowed by the restricted host type. For example, if you had a restricted host type that only allows LUNs up to 31, you cannot move that restricted host type into a partition that has LUNs greater than 31 already mapped.
You cannot change an HBA host port to a restricted host type if there are already virtual disk-to-LUN mappings in the partition that would exceed the limit imposed by the restricted host type.
If the Default Group has access to LUNs up to 256 (0 to 255) and a restricted host type is added to the Default Group, the host associated with the restricted host type is able to only access virtual disks in the Default Group with LUNs within its limits. For example, if the Default Group had two virtual disks mapped to LUNs 254 and 255, the host with the restricted host type would not be able to access those two virtual disks.
If the Default Group has a restricted host type assigned and the storage partitions are disabled, only a total of 32 LUNs can be mapped. Any additional virtual disks created will be put in the Unidentified Mappings area. If additional mappings are defined for one of these Unidentified Mappings, the Define Additional Mapping dialog shows the LUN list and the Add button as unavailable.
The Default Group in the has a default host type. You can change this type by selecting Storage Array >> Change >> Default Host Type. If you set the default host type to a host type that is restricted, the maximum LUNs allowed in the Default Group for any host are restricted to the limit imposed by the restricted host type. If a particular host with a non-restricted host type becomes part of a specific partition, then you are able to change the mapping to a higher LUN.