Avatar of deanwilsons
deanwilsons
Flag for United Kingdom of Great Britain and Northern Ireland asked on

ESX5.5 in IBM S Chassis connecting to SAS LUN

Hi,

We have just bought a HS23 Blade, that is installed into an S Chassis along with 5 existing HS21 blades.

Four of the existing blades all boot ESXi5.5 from the SAN and have read write access to 2 shared LUNs (ID 0 and 1) which are used as datastores for ESX.
We have Vcenter 5.5 and all the ESX hosts including the HS23 are part of that cluster.

The SCM is zoned correctly for bay 6, which is the bay that the HS23 is installed in, and the LUNs are displayed in ESX, but they are not showing as datastores.

There is 1 thing that i noticed, and thats the local drive is set to LUN 0 as well, but even when i remove access to LUN 0 from the SAN i cannot access the remaining LUN which is ID 1.

output from cli command "esxcli storage core path list"

sas.500507604d2108dc-sas.96c7e46b0838a18-naa.600508e000000000188a83b0467e6c09
   UID: sas.500507604d2108dc-sas.96c7e46b0838a18-naa.600508e000000000188a83b0467e6c09
   Runtime Name: vmhba0:C1:T0:L0
   Device: naa.600508e000000000188a83b0467e6c09
   Device Display Name: LSI Serial Attached SCSI Disk (naa.600508e000000000188a83b0467e6c09)
   Adapter: vmhba0
   Channel: 1
   Target: 0
   LUN: 0
   Plugin: NMP
   State: active
   Transport: sas
   Adapter Identifier: sas.500507604d2108dc
   Target Identifier: sas.96c7e46b0838a18
   Adapter Transport Details: 500507604d2108dc
   Target Transport Details: 96c7e46b0838a18
   Maximum IO Size: 4194304

sas.500507604d2108dc-sas.5005076b074f1820-naa.6005076b07498b7f4ab0e8610000000a
   UID: sas.500507604d2108dc-sas.5005076b074f1820-naa.6005076b07498b7f4ab0e8610000000a
   Runtime Name: vmhba0:C0:T2:L0
   Device: naa.6005076b07498b7f4ab0e8610000000a
   Device Display Name: IBM Serial Attached SCSI Disk (naa.6005076b07498b7f4ab0e8610000000a)
   Adapter: vmhba0
   Channel: 0
   Target: 2
   LUN: 0
   Plugin: NMP
   State: active
   Transport: sas
   Adapter Identifier: sas.500507604d2108dc
   Target Identifier: sas.5005076b074f1820
   Adapter Transport Details: 500507604d2108dc
   Target Transport Details: 5005076b074f1820
   Maximum IO Size: 4194304

sas.500507604d2108dc-sas.5005076b074f1820-naa.6005076b07498b7f4b214a7f0000000b
   UID: sas.500507604d2108dc-sas.5005076b074f1820-naa.6005076b07498b7f4b214a7f0000000b
   Runtime Name: vmhba0:C0:T2:L1
   Device: naa.6005076b07498b7f4b214a7f0000000b
   Device Display Name: IBM Serial Attached SCSI Disk (naa.6005076b07498b7f4b214a7f0000000b)
   Adapter: vmhba0
   Channel: 0
   Target: 2
   LUN: 1
   Plugin: NMP
   State: active
   Transport: sas
   Adapter Identifier: sas.500507604d2108dc
   Target Identifier: sas.5005076b074f1820
   Adapter Transport Details: 500507604d2108dc
   Target Transport Details: 5005076b074f1820
   Maximum IO Size: 4194304

and  "esxcli storage vmfs extent list" shows only 1 datastore

Volume Name     VMFS UUID                            Extent Number  Device Name                           Partition
--------------  -----------------------------------  -------------  ------------------------------------  ---------
datastore1 (5)  546f54ea-41b4c172-3c41-3640b5e87697              0  naa.600508e000000000188a83b0467e6c09          3


The only option i get is to create a new datastore, but thats not an option as i have production machines on those LUNs.

any help would be great.
VMwareVirtualizationStorage

Avatar of undefined
Last Comment
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

8/22/2022 - Mon
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

what is the output from

esxcfg-volume -l

is the LUN present in Storage Adaptors?

but is it the datastore just missing?
deanwilsons

ASKER
hi

the out put is

~ # esxcfg-volume -l
VMFS UUID/label: 4ab168d0-e28693f8-c443-00215e618b60/TM13-IBMS-SAN-01
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.6005076b07498b7f4ab0e8610000000a:1      range: 0 - 1204991 (MB)

VMFS UUID/label: 4b253daf-80177ac8-c495-00215e618b5e/TM13-IBMS-SAN-02
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.6005076b07498b7f4b214a7f0000000b:1      range: 0 - 2017023 (MB)


in the storage adapter they are there as shown in the attachment, but not available as datastores.

i did reboot of a working host to make sure the datastores were still available after a reboot.

thanks

Phil
storage-adapter.JPG
ASKER CERTIFIED SOLUTION
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
deanwilsons

ASKER
hi Andrew,

that worked a treat, many thanks.

Couple of questions though.

Is this the normal procedure for adding a new host into the SAS storage, as i have only dealt with Iscsi and fibre sans before, and never come across this issue with those.

If its not normal behaviour, is there a chance it will refuse to mount correctly after a reboot even with the -M switch?

thanks

Phil
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

This is often the issue.,...

I would not say normal, but some hosts, on all versions of VMware vSphere "do get stuck" sometimes, on iSCSI and FC, and the GUI does not seem to be able to help with this situation.

It's normal enough for us to see it, but I suppose that depends on how many vSphere installations and storage systems you deal with on a weekly basis.

the -M is supposed to be a --persistent mount, rather than -m, which is not.

At next reboot check!
deanwilsons

ASKER
Thanks very much Andrew.

regards

Phil
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

that's not a problem.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.