Term
| What is the role of a hardware iSCSI adapter? |
|
Definition
| Offloads the network and iSCSI processing from the host |
|
|
Term
| Define a dependent hardware iSCSI adapter |
|
Definition
* Depends on VMware networking and the iSCSI management interfaces within VMware
* Depends upon the host's network configuration for IP and MAC
* Management interfaces are provided by VMware |
|
|
Term
| Define an independent hardware iSCSI adapter |
|
Definition
* Independent from the host and VMware - implements its won management interface
* Provides its own configuration management for IP and other network address assignment |
|
|
Term
| Define a software iSCSI adapter |
|
Definition
| Software iSCSI adapters are built into the VMkernel. A standard NIC installed on the host can be used to connect to iSCSI targets. Network processing and encapsulation are performed on the host. |
|
|
Term
| Outline the steps to configure/edit independent HW iSCSI initiators |
|
Definition
1. Check whether the adapter needs a license with the vendor
2. Install the adapter referring to vendor documentation
3. Verify correct installation. If installed correctly, it will be listed in Storage Adapter section of the Configuration tab of the host
4. Configure Discovery information
5. Configure CHAP Parameters |
|
|
Term
| Outline the steps to configure/edit dependent HW iSCSI initiators |
|
Definition
1. View the dependent adapter - check the Storage Adapters section of the configuration tab of the host. If your adapter isn't listed, ensure that it has a valid license - vendor documentation
2. Determine the association between dependent HW adapters and physical NICs. Select the appropriate adapter and click 'Properties'. From here, select the Network Configuration tab and click 'Add'. Add the corresponding nic to the adapter.
3. Configure Networking for iSCSI
4. Configure Discovery Information
5. Configure CHAP |
|
|
Term
| Is a SW iSCSI initiator enabled or disabled by default? |
|
Definition
| Disabled, it must be activated. |
|
|
Term
| How many SW iSCSI initiators can be activated per host? |
|
Definition
| Only one SW initiator can be activated per host |
|
|
Term
| Outline the steps to enable/disable a SW iSCSI initiator |
|
Definition
| Look on the host's 'configuration' tab. Go to the storage adapter section and find the SW initiator. Right click it and select 'Properties'. Click 'Configure' and check/uncheck the Enabled checkbox |
|
|
Term
| How do you configure/edit settings on your software iSCSI initiator? |
|
Definition
| Right click your storage adapter and select 'properties' |
|
|
Term
| What four tabs are available to edit settings on a SW iSCSI initiator? What do they allow you to do? |
|
Definition
1. General tab: change the status, iSCSI name and alias, CHAP settings, advanced
2. Network Configuration tab: Allows you to configure port bindings and select the port group to be associated with software iSCSI stack
3. Dynamic Discovery: Also known as send targets - when the initiator contacts a specified server, the initiator sends the SendTargets request to it. The server will respond by supplying a list of available targets back. The names and IPs of the targets will appear on the Static Discovery tab. If you remove one of these from Static Discovery, it will probably reappear next time a rescan happens, an hba is reset, or the host rebooted.
3. Static Discovery Tab: No discovery is performed. Need to manually input the target names and the associated IP Address. Click 'Add' to specify the target server name or IP, port and associated target name (IQN) |
|
|
Term
| Where do you configure iSCSI port binding? |
|
Definition
| In the Network Configuration tab found when you right click your SW iSCSI adapter and select 'properties'. |
|
|
Term
| What does iSCSI port binding allow you to do? |
|
Definition
| Select the port group containing the vmkernel port that you wish to bind your SW iSCSI stack to. If you were using a HW initiator, only the vmkernel port associated wit the initiators corresponding NIC will be available |
|
|
Term
| T/F: ESXi supports mutual CHAP for all types of initiators |
|
Definition
| False: ESXi Supports one-way CHAP for all types of initiators and mutual CHAP for software and dependent hardware initiators |
|
|
Term
| In which direction does one way CHAP authenticate? |
|
Definition
| Target authenticates initiator |
|
|
Term
| Name the four CHAP Security Levels |
|
Definition
| Do not use CHAP, Do not use CHAP unless required by the target, Use CHAP unless prohibited by target, Use CHAP |
|
|
Term
| What happens if you select 'Do not use CHAP'? |
|
Definition
| Chap authentication will not be used. This is supported across all initiators |
|
|
Term
| What happens if you select 'Do not use CHAP unless required by the target'? |
|
Definition
| The host will prefer a non-CHAP connection, but can use CHAP if the target requires. Supported only on software and dependent hardware initiators |
|
|
Term
| What happens if you select 'Use CHAP unless prohibited by the target'? |
|
Definition
| The host will prefer CHAP but if the target does not support or use it, it can use non CHAP. Supported across all initiators |
|
|
Term
| What happens if you select 'Use Chap'? |
|
Definition
| The host will require a successful CHAP connection. Supported only on software and independent hardware initiators |
|
|
Term
| In what circumstances would you use an Independent Hardware Initiator? |
|
Definition
| You would want to use a hardware initiator if running production storage through iSCSI that requires a lot of I/O. Using hardware iSCSI will offload most of the work from vSphere to the initiator. |
|
|
Term
| In what circumstances would you use a Dependent Hardware Initiator? |
|
Definition
| You might have NICs that currently support this mode of iSCSI, in which it would make more sense to use this than a software initiator |
|
|
Term
| In what circumstances would you use a software initiator? |
|
Definition
| Unless you have a good reason not to, this is a low cost option as you can use your existing NICs. |
|
|
