Automating Storage Connection to Existing StorageGroup for New ESXi Host

Question

I am in the process of automating the storagegroup connection to a newly provisioned ESXi Host.  Here are the steps I am currently following.  The storeagegroup has already be defined and attached to existing ESXi Host in a cluster.  It is also a shared storagegroup Do you see any specific commands that are being missed? Brocade: 1.  Create Alias for each HBA on the ESXi Host.using WWNs. 2.  Created Zoning and Configuation Zones on Switch. NavIseccli: 1.  Ran the following command to set path to existing Storagegroup and Host.  Ran 4 time, twice for each HBA.                naviseccli -h %host_navi% -User %user% -Password %pass% -Scope 0 storagegroup -setpath -o -gname -hbauid <*> -sp a -spport 0 -type 3 -ip -host -failovermode 4 -arraycommpath 1                     * - combined PortWorldWideName + ':' + NodeWorlWideName queried from vCenter and teh ESXi Host. 2.  Connect Host to Storagegroup                naviseccli -h %host_navi% -User %user% -Password %pass% -Scope 0 storagegroup -connecthost -host -gname -o vCenter: RescanHBA Results:  New Storage does not appear as expected, even when in NaviSphere the connections are shown as logged in and registered. Frank Wall Senior Consultant

dynamox · Answer

oh yeah ..make sure to register in nodeWWN:portWWN format.

FWALL-WINDWARD · Answer

I am trying to see the Devices and Paths show up as they do on the existing ESXi Host in the cluster.

dynamox · Answer

what do you expect to see ?

FWALL-WINDWARD · Answer

Yes I am following the format you mentioned.  In the NaviSphere Console we are seeing the 4 connection as logged in and registered as shown in the image attached.

dynamox · Answer

fwall-windward wrote: I am trying to see the Devices and Paths show up as they do on the existing ESXi Host in the cluster. devices and paths of ESX host in Unisphere ?

FWALL-WINDWARD · Answer

This would appear on the Storage Adapter screen in the vSphere client.  On the other host in the cluster they appeared after performing a ReScan on all HBAs.

FWALL-WINDWARD · Answer

Per the Storage Admin at the customer I am working he says it looks the same as the existing ESXi Host that has been discovered. The initial attached image show what he gave to me. All I have access to is the naviseccli command interface I am using in the automation steps.

if you look at storage_img_02.jpg I have attached you will see the results of the port -list -gname for the new host. It matches the other host expect for values in the HBA Devicename and other fields that should be specific to this host and HBAs values.

1 Attachment

storage_img_02.jpg

dynamox · Answer

when you select Connectivity Details in Unisphere, things look ok ?

dynamox · Answer

interesting, this is adding new host to an existing storage group?&#xa0; Do you know if he/she select both options when rescanning ?

dynamox · Answer

Mark May wrote: I've had the exact same issues with needing to upgrade code before a lun would show up.  Are you behind HP Flex? nope, MDS 9124e in NPV mode

cincystorage · Answer

I've had the exact same issues with needing to upgrade code before a lun would show up. Are you behind HP Flex?

dynamox wrote:

a couple of week ago i had an issue with HP C-class blade that exhibited something similar to your problem, i asked them to flash firmware on the mezzanine card (on-board HBA), bounced the box and it was fine. I know it's a long shot but i wanted to share anyway.

dynamox · Answer

can you re-register and in addition to failover mode, initiator type also use '-unitserialnumber array'

dynamox · Answer

have not used it, anything specific in host profiles ?

dynamox · Answer

PXE boot ?

FWALL-WINDWARD · Answer

Per the VMWare Admin not to my knowledge.  We autodeployed the other server in the cluster and it worked fine.  The difference is the Storage Admin added the storage through a GUI.

CLARiiON

Was this post helpful?