Administrator Guide

Rename a host group

You can rename a host group.

1. In the Hosts topic, select a host group to rename.

2. Select Action > Rename Host Group. The Rename Host Group panel opens.

3. In the New Host Group Name field, enter a new name for the host group. A host group name is case sensitive and can have a

maximum of 32 bytes. It cannot already exist in the system or include the following: " , . < \

If the name is used by another host group, you are prompted to enter a different name.

4. Click OK. The hosts table is updated.

Remove host groups

You can remove host groups. Removing a host group will ungroup its hosts but will not delete them.

1. In the Hosts topic, select 1 through 32 host groups to remove.

2. Select Action > Remove Host Group. The Remove Host Group panel opens and lists the host groups to be removed.

3. Click OK. For hosts that were in the selected host groups, the Group value changes to --.

Configuring CHAP

For iSCSI, you can use Challenge-Handshake Authentication Protocol (CHAP) to perform authentication between the initiator and target

of a login request. To perform this identification, a database of CHAP records must exist on the initiator and target. Each CHAP record

can specify one name-secret pair to authenticate the initiator only (one-way CHAP) or two pairs to authenticate both the initiator and the

target (mutual CHAP). For a login request from an iSCSI host to a controller iSCSI port, the host is the initiator and the controller port is

the target.

When CHAP is enabled and the storage system is the recipient of a login request from a known originator (initiator), the system will

request a known secret. If the originator supplies the secret, the connection will be allowed.

To enable or disable CHAP for all iSCSI nodes, see Changing host port settings on page 51.

Special considerations apply when CHAP is used in a system with a peer connection, which is used in replication. In a peer connection, a

storage system can act as the originator or recipient of a login request. As the originator, with a valid CHAP record it can authenticate

CHAP even if CHAP is disabled. This is possible because the system will supply the CHAP secret requested by its peer and the connection

will be allowed. For information about setting up CHAP for use in a peer connection and how CHAP interacts with replication, see Creating

a peer connection on page 119.

Add or modify a CHAP record

1. If you intend to use mutual CHAP and need to determine the IQN of a controller iSCSI port, perform the following:

• Select the System topic.

• Select the Rear view.

• Hover the cursor over the iSCSI host port that you intend to use. In the Port Information panel that appears, note the IQN in the ID

field value.

2. In the Hosts topic, select Action > Configure CHAP. The Configure CHAP panel opens with existing CHAP records listed.

3. Select the Enable Authentication (CHAP) checkbox to enable use of CHAP for all iSCSI nodes, then confirm the operation.

NOTE:

Enabling or disabling CHAP here will update its setting in the Advanced Settings tab in the Host Ports

Settings panel.

4. Perform one of the following:

• To modify an existing record, select it. The record values appear in the fields below the CHAP records list for editing. You cannot

edit the IQN.

• To add a new record, click New.

5. For a new record, in the Node Name (IQN) field, enter the IQN of the initiator. The value is case sensitive and can include a maximum

of 223 bytes, including 0–9, lowercase a–z, hyphen, colon, and period.

6. In the Secret field, enter a secret for the target to use to authenticate the initiator. The secret is case sensitive and can include 12–16

bytes. The value can include spaces and printable UTF-8 characters except for the following: " <

Working in the Hosts topic