-
Click on the + in the upper right hand corner of the Hosts section to open the Create Host dialog box. Give the new host a name and select a host personality if appropriate, otherwise leave the default value of "None".
-
Select the newly created host. Click the 'vertical ellipsis' icon within the Host Ports panel and select Configure WWNs.
-
The Configure Fibre Channel WWNs for Host dialog box will open. Select the WWNs from the Existing WWNs list. To identify the proper WWNs for a host refer to How-To: Retrieve World Wide Names (WWNs) and iSCSI Qualified Names (IQNs) on Windows Server.
Note:
With a properly configured fabric that has a Everpure FlashArray connected the WWNs for all the hosts connected to the fabric will be displayed in the Existing WWNs list. If they do not show up and it is necessary to enter them manually refer to How-To: Retrieve World Wide Names (WWNs) and iSCSI Qualified Names (IQNs) on Windows Server.
6. Click on the + in the Volumes section to create a volume. For this example, the name FC-TestVolume with a size of 500 G is being used. A different name and size can be used. Specify values for bandwidth and/or IOPS limits if desired.
7. After creating the new volume, navigate back to the Hosts view and select the host. Within the Connected Volumes pane click the 'vertical ellipsis' icon and select the Connect... menu item.
8. The Connect Volumes to Host dialog will open. Click on the FC-TestVolume (or whatever volume name was created) then click Connect.
9. Now the new host is connected to the new volume, FC-TestVolume, with the host WWNs configured.
10. In the FlashArray Management interface, select Health from the lefthand menu and then click Connections. Within the Host Connections pane, select the host that was just configured. The Connection Map for Host dialog should show Redundant connections.
Note:When all volumes are disconnected from a host, the FlashArray will disconnect the session to the initiator and wait for the initiator's commands to re-establish the session, a new session will be created with the next initiator request from the host. If the initiator doesn't log back in, the Host Port Connectivity for this initiator will show connections as grayed out.
By removing the session we guarantee that both the target and initiator understand the channel is closed and no more data can be sent down it. This is a protection against unexpected re-use of the session.