Solved

ESX5.5 in  IBM S Chassis connecting to SAS LUN

Posted on 2014-11-21
7
450 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 120
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 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 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
Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

 

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 120
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 120
ID: 40461771
that's not a problem.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

Suggested Solutions

Each year, investment in cloud platforms grows more than 20% (https://www.immun.io/hubfs/Immunio_2016/Content/Marketing/Cloud-Security-Report-2016.pdf?submissionGuid=a8d80a00-6fee-4b85-81db-a4e28f681762) as an increasing number of companies begin to…
Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…

734 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