Administrator Guide

You cannot use the Group Manager GUI to enable or disable iSNS discovery for a volume or snapshot. Instead, you must use the
following CLI command lines:
volume select volume_name isns-discovery enable | disable
volume select
volume_name snapshot select snapshot_name isns-discovery enable | disable
Congure an iSNS Server in the Group
To congure an iSNS server:
1. Click Group → Group Conguration.
2. Click the iSCSI tab.
3. In the iSCSI Discovery panel, click Add to open the iSNS Server dialog box.
4. Specify the IP address and optional port for an iSNS server and click OK. (The default port setting is 3205.)
5. Repeat steps 3 and 4 to add up to two additional servers.
NOTE: To prevent hosts from discovering iSCSI targets that do not have the correct CHAP credentials, select the
Prevent unauthorized hosts from discovering targets checkbox.
Modify an iSNS Server
To modify the IP address for an iSNS server:
1. Click Group → Group Conguration.
2. Click the iSCSI tab.
3. In the iSCSI Discovery panel, select the address and click Modify.
4. Change the IP address as needed.
5. Click OK.
6. Click Save all changes.
Delete an iSNS server
To delete the IP address for an iSNS server to remove the server from the conguration:
1. Click Group → Group Conguration.
2. Click the iSCSI tab.
3. In the iSCSI Discovery panel, select the server’s IP address.
4. Click Delete.
5. When prompted to conrm the decision, click Yes.
Prevent Discovery of Unauthorized Targets
By default, iSCSI initiators that use discovery try to log in to group targets protected by CHAP, even if they do not have the correct
access credentials. These attempts can result in a large number of events logged in the group and is not an ecient use of
resources.
You can prevent computers from discovering unauthorized targets by enabling the iSCSI discovery lter. If you enable the iSCSI
discovery lter, initiators discover only those targets for which they have the correct access credentials.
iSCSI Access Requirements
To access an iSCSI target (for example, a volume or snapshot), an iSCSI initiator must meet the security requirements identied in
Table 22. Access Requirements for iSCSI Targets.
About Volume-Level Security
121