Administrator Guide

3. Enter the destination port address for the remote system.
4. Enter the name and password of a user with the manage role on the remote system.
5. Click OK.
6. If the task succeeds, click OK in the confirmation dialog. The peer connection is created and the Peer Connections table is
updated.
If the task does not succeed, the Create Peer Connection panel appears with errors in red text. Correct the errors, then click
OK.
CHAP and replication
If you want to use Challenge Handshake Authentication Protocol (CHAP) for the iSCSI connection between peer systems,
see the procedure below to set up CHAP. Make sure that you configure both systems in this way. In a peer connection,
both systems will alternately act as an originator (initiator) and recipient (target) of a login request. Peer connections support
one-way CHAP only.
If only one system has CHAP enabled and the two systems do not have CHAP records for each other, or the CHAP records
have different secrets, the system with CHAP enabled will be able to modify the peer connection. However, it will be unable
to perform any other replication operations, such as creating replication sets, initiating replications, or suspending replication
operations. The system that does not have CHAP enabled will be unable to perform any replication operations, including
modifying and deleting the peer connection. For full replication functionality for both systems, set up CHAP for a peer
connection (see the following procedure).
If the two systems have CHAP records for each other with the same secret, they can perform all replication operations whether
or not CHAP is enabled on either system. In other words, even if CHAP is enabled on neither system, only one system, or both
systems, either system can work with peer connections, replication sets, and replications.
If you want to use Challenge Handshake Authentication Protocol (CHAP) for the iSCSI connection between peer systems, see
the following procedure to set up CHAP. In a peer connection, both systems will alternately act as an initiator and target of a
login request. Peer connections support one-way CHAP only.
Set up CHAP for a peer connection using the CLI
1. If you have not already configured CHAP, run query peer-connection from either the local system or the remote
system to ensure that they have connectivity.
2. If you have an existing peer connection, stop I/O to it.
3. On the local system, use the create chap-record command to create a CHAP record for one-way CHAP to allow
access by the remote system.
4. On the remote system, use the create chap-record command to create a CHAP record for one-way CHAP to the local
system. Note that the same CHAP record used from the local system may also be used here but the configuration is still
one-way CHAP.
5. On each system, enable CHAP by running: set iscsi-parameters chap on
CAUTION:
Enabling or disabling CHAP will cause all iSCSI host ports in the system to be reset and restarted.
This may prevent iSCSI hosts from being able to reconnect if their CHAP settings are incorrect.
6. Wait one minute for the commands to complete before attempting to use the peer connection.
7. Run query peer-connection from the local system and then from the remote system to ensure communication can be
initiated from either system.
● If both succeed, you can create, set, or perform replication on that peer connection.
● If either fails, it is likely that you must fix a CHAP configuration issue and then repeat these steps as appropriate. If you
need to modify a CHAP record, use the set chap-record command.
Modifying a peer connection
You can change the name of a current peer connection or the port address of the remote system from either the local system
or the remote system without changing the peer connection configurations. For example, you could configure a peer connection
and then move one of the peers to a different network.
126
Working in the Replications topic