24 Getting started
• Enable CHAP on the storage system. Note that this applies to all iSCSI hosts, in order to avoid security
exposures.
• Define CHAP secret in the host iSCSI initiator.
• Request host login to the storage system. The host should be displayable by the system, as well as the
ports through which connections were made.
If it becomes necessary to add more hosts after CHAP is enabled, additional CHAP node names and
secrets can be added. If a host attempts to login to the storage system, it will become visible to the system,
even if the full login is not successful due to incompatible CHAP definitions. This information may be useful
in configuring CHAP entries for new hosts. This information becomes visible when an iSCSI discovery
session is established, because the storage system does not require discovery sessions to be authenticated.
Related topics
• Using the Configuration Wizard on page 37
• Changing host interface settings on page 46
• Adding a host on page 74
• Removing hosts on page 75
• Changing a host's name on page 75
• Changing host mappings on page 75
• Viewing information about a host (page 99) or all hosts (page 98)
About volume mapping
Each volume has default host-access settings that are set when the volume is created; these settings are
called the default mapping. The default mapping applies to any host that has not been explicitly mapped
using different settings. Explicit mappings for a volume override its default mapping.
Default mapping enables all attached hosts to see a volume using a specified LUN and access permissions
set by the administrator. This means that when the volume is first created, all connected hosts can
immediately access the volume using the advertised default mapping settings. This behavior is expected by
some operating systems, such as Microsoft Windows, which can immediately discover the volume. The
advantage of a default mapping is that all connected hosts can discover the volume with no additional
work by the administrator. The disadvantage is that all connected hosts can discover the volume with no
restrictions. Therefore, this process is not recommended for specialized volumes that require restricted
access.
You can change a volume's default mapping, and create, modify, or delete explicit mappings. A mapping
can specify read-write, read-only, or no access through one or more controller host ports to a volume.
When a mapping specifies no access, the volume is masked. You can apply access privileges to one or
more of the host ports on either controller. To maximize performance, map a volume to at least one host
port on the controller that owns it. To sustain I/O in the event of controller failure, map to at least one host
port on each controller.
For example, a payroll volume could be mapped with read-write access for the Human Resources host and
be masked for all other hosts. An engineering volume could be mapped with read-write access for the
Engineering host and read-only access for other departments’ hosts.
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 per volume as its default LUN.
For example, if LUN 5 is the default for Volume1, 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.
TIP: When an explicit mapping is deleted, the volume’s default mapping takes effect. Therefore, it is
recommended to use the same LUN for explicit mappings as for the default mapping.
To Next Page
Loading...
Need help?
General
