23.03.2013 Views

VessRAID Setup - Promise Technology, Inc.

VessRAID Setup - Promise Technology, Inc.

VessRAID Setup - Promise Technology, Inc.

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

•<br />

181<br />

Chapter 5: Management with the CLU<br />

5. Highlight, press the backspace key to erase the current value, and type a<br />

value for each of the following items:<br />

• iSNS Server IP address<br />

• iSNS Server Port number (3205 for most applications)<br />

6. Press Ctrl-A to save your settings.<br />

Working with iSCSI CHAPs<br />

Note<br />

Edge Side <strong>Inc</strong>ludes (ESI) is a markup language that enables<br />

dynamic assembly of web page elements in servers across a<br />

network. This feature enables automatically if iSNS is enabled and<br />

an iSNS server is present.<br />

Challenge Handshake Authentication Protocol (CHAP) is an authentication<br />

mechanism used to authenticate iSCSI sessions between initiators and targets.<br />

The authenticator sends the peer a challenge message to request authentication<br />

consisting of a sequence number and a random number. Both the sender and<br />

peer share a predefined secret or password. The peer concatenates the<br />

sequence number, the random value, and the secret and calculates a hash using<br />

a one-way hash algorithm such as MD5. The peer sends the hash value back to<br />

the authenticator, which in turn builds that same string on its side, calculates the<br />

hash, and compares the result with the value received from the peer. If the values<br />

match, the peer is authenticated. The authenticator then initiates CHAP sessions<br />

at random time intervals incrementing the sequence number each new challenge<br />

session to protect against replay attacks.<br />

With <strong>Promise</strong> subsystems, CHAP secrets cannot be assigned to individual<br />

LUNS. Use LUN mapping and masking to restrict LUN access to a unique<br />

initiator. A single target CHAP secret should not be shared among multiple<br />

initiators.<br />

Note<br />

Enable CHAP Authentication under iSCSI Node settings. See<br />

page 177.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!