![]() The volume can now be used as a Raw Device Map or a Datastore. On the array I can now see all 8 paths under Manage -> Connections. The Active(I/O) paths are going to the active controller and the Standby paths are for the standby controller. I have 4 Active(I/O) paths and 4 Standby paths. The PSP should be set to NIMBLE_PSP_DIRECTED. ![]() ![]() Looking at the path details for LUN 87, you can 8 paths (2HBA’s x 4 Target Ports). Now, the volume is created on the array and your initiators are set-up to allow connection from your FC HBA on the host to connect.Īfter a rescan of the FC HBA, I can see my LUN with the ID 87. Specify any protection schedule if required and click on Finish to create the volume. Next, specify the size and reservation settings for the volume. This will allow your hosts to connect to the newly created volume.Īlso, specify a unique LUN ID. Name your new initiator group and specify the WWNs of your ESXi hosts. If you don’t have an initiator group yet, click on New Initiator Group. Next, select the initiator group which has the information of your ESXi host. Specify the Volume Name, Description and select the proper Performance Policy for proper block alignment. ![]() Go to Manage -> Volumes and click on New Volume. The steps are fairly similar to integrating a Nimble iSCSI array but there are some more FC specific settings which need to be set.įirst, go ahead and create a new volume on your array. This post will cover the integration of a Nimble Storage Fibre Channel array in a VMware ESXi environment.
0 Comments
Leave a Reply. |