Term
| What types of initiators are supported for one-way CHAP? |
|
Definition
| All types of iSCSI initiators (software, dependent hardware and independent hardware) |
|
|
Term
| What types of initiators are supported for mutual CHAP? |
|
Definition
| Software and dependent hardware iSCSI initiators only |
|
|
Term
| Where should CHAP be enabled first, on the ESXi host, or on the iSCSI storage system? |
|
Definition
| Before configuring CHAP, check whether CHAP is enabled at the iSCSI storage system and check the CHAP authentication method the system supports. If CHAP is enabled on the target, enable it for your initiators, making sure that the CHAP authentication credentials match the credentials on the iSCSI storage. |
|
|
Term
| In which direction does one-way CHAP work? |
|
Definition
| In one way CHAP (unidirectional) authentication, the target authenticates the initiator, but the initiator does not authenticate the target |
|
|
Term
| For software and dependent hardware iSCSI adapters, where can you set the CHAP policy? |
|
Definition
| You can set the CHAP policy for software and dependent hardware adapters for each initiator or at the target level. |
|
|
Term
| For independent hardware iSCSI adapters, where can you set the CHAP policy? |
|
Definition
| Independent hardware iSCSI supports CHAP only at the initiator level. |
|
|
Term
| T/F: When specifying CHAP security level the actions performed by the array are set at the vSphere level and are array-vendor neutral |
|
Definition
| False: When you specify the CHAP security level, how the storage array responds depends on the array’s CHAP implementation and is vendor specific. For example, when you select Use CHAP unless prohibited by target, some storage arrays use CHAP in response, while others do not. For information on CHAP authentication behavior in different initiator and target configurations, consult the array documentation. |
|
|
Term
| Name the 4 CHAP security levels and supported adapter types for each |
|
Definition
1. Do not use CHAP - SW, Dependent HW, Independent HW
2. Do not use CHAP unless required by the target - SW, Dependent HW
3. Use CHAP unless prohibited by the target - SW, Dependent HW, Independent HW
4. Use CHAP - SW, Dependent HW |
|
|
Term
| What happens if you select 'Do not use CHAP', and which adapters are supported? |
|
Definition
| The host does not use CHAP authentication. Select this option to disable authentication if it is currently enabled. Supported by SW, Dependent HW and Independent HW |
|
|
Term
| What happens if you select 'Do not use CHAP unless required by the target', and which adapters are supported? |
|
Definition
| the host prefers a non-CHAP connection, but can use a CHAP connection if required by the target. Used by SW and Dependent HW adapters |
|
|
Term
| What happens if you select 'Use CHAP unless prohibited by the target', and which adapters are supported? |
|
Definition
| The host prefers CHAP, but can use non-CHAP connections if the target does not support CHAP. |
|
|
Term
| What happens if you select 'Use CHAP', and which adapters are supported? |
|
Definition
| The host requires successful CHAP authentication. The connection fails if CHAP negotiation fails. Used by SW and Dependent HW adapters only. |
|
|
Term
| If an ESXi host is configured to access an iSCSI target using CHAP authentication, what happens to access if CHAP is disabled on an ESXi host? |
|
Definition
| The host will remain connected as long as the connection continues since CHAP is only checked when the connection is made. If either host or array ends the connection, re-connect will fail |
|
|
