Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

ESX5.5 in  IBM S Chassis connecting to SAS LUN

Posted on 2014-11-21
7
Medium Priority
?
467 Views
Last Modified: 2014-11-24
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.
0
Comment
Question by:deanwilsons
  • 4
  • 3
7 Comments
 
LVL 124
ID: 40457953
what is the output from

esxcfg-volume -l

is the LUN present in Storage Adaptors?

but is it the datastore just missing?
0
 

Author Comment

by:deanwilsons
ID: 40458235
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
0
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40458304
are these the datastores missing?

TM13-IBMS-SAN-01
TM13-IBMS-SAN-02

type

esxcfg-volume -m TM13-IBMS-SAN-01 (or -M)

esxcfg-volume -m TM13-IBMS-SAN-02 (or -M)

and you  an use the persistent command

-m | --mount <vmfs uuid|label>
-M | --persistent-mount <vmfs uuid|label>
0
Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as high-speed processing of the cloud.

 

Author Comment

by:deanwilsons
ID: 40461603
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
0
 
LVL 124
ID: 40461664
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!
0
 

Author Comment

by:deanwilsons
ID: 40461760
Thanks very much Andrew.

regards

Phil
0
 
LVL 124
ID: 40461771
that's not a problem.
0

Featured Post

Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many businesses neglect disaster recovery and treat it as an after-thought. I can tell you first hand that data will be lost, hard drives die, servers will be hacked, and careless (or malicious) employees can ruin your data.
August and September have been big months for VMware—from VMworld last month to our new Course of the Month in VMware Professional - Data Center Virtualization. We reached out to Andrew Hancock, resident VMware vExpert, to have a more in-depth discu…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…
Despite its rising prevalence in the business world, "the cloud" is still misunderstood. Some companies still believe common misconceptions about lack of security in cloud solutions and many misuses of cloud storage options still occur every day. …

971 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question