MSA 2026 - how to set up mapping in hp msa 2060 by analogy as in the 2050 model

[Kurennov_Igor]

Default mappings for volumes on MSA 2050

By default, the HPE MSA maps all connected initiators to all volumes/volume groups. Therefore, all hosts/host groups have the ability to access
all volumes using the specified access mode, LUN, and port settings. This is considered the default mapping.
The advantage of the default mapping is that all connected hosts can discover all volumes and volume groups with no additional work by the
administrator. The disadvantage is that all connected hosts can discover volumes with no restrictions. Therefore, this process is not
recommended for specialized volumes, which require restricted access. In clustered environments, to avoid multiple hosts mounting the volume
and causing corruption, the hosts must be cooperatively managed using cluster software.
You can change the default mapping of a volume, or create, modify, and delete explicit mappings. A mapping can specify read-write, read-only, or
no access to a volume through one or more controller host ports. When a mapping specifies no access, the volume is masked.
When creating an explicit mapping from a host/host group to a volume/volume group, a LUN identifier is established. A LUN identifies a mapped
volume to a host. Both controllers share a set of LUNs, and any unused LUN can be assigned to a mapping. However, each LUN can only be used
once as a default LUN. For example, if LUN 5 is the default for Volume 1, no other volume in the storage system can use LUN 5 as its default
LUN. For explicit mappings, the rules differ: LUNs used in default mappings can be reused in explicit mappings for other volumes and other
hosts.

[JonPaul]

There is no longer a concept of default mapping in the MSA 2060.  This form of mapping was helpful for a few but detrimental to many.  All maps (now called attachment) are explicit.