Data Storage from FC SAN not consumed

[Khai Nguyen]

Dear all, I have a host ESXi 6.7.0 build-17167734 managed by vCenter (6.7.0.51000 build 18831133). A few days ago, I had a mapping of some volumes from an IBM SAN (FC mapping) to create datastorage for the hosts, everything is working properly, but suddenly one of the hosts shows a ''not consumed'' status with some previously mapped datastorage, athought operational status is attached, I wait a few minutes and try to rescan the datastorage again, the datastorage shows again. but I am afraid that this error will happen again and will affect the system operation. Can you explain this to me?

 

[Hiep Au]

I have a trouble the same. Please support!!!!

[E_Espinel]

Hello.
more details are required such as:
the IBM Storage FS5035 firmware
The model and P/N of the HBA (FC Card)
The firmware and drive of the HBA
The type and model of the physical server
Is the connection between the Server and the Storage direct or does it use FC Switch ?

Is the compatibility of the FS5035, HBA, FC Switch and Server validated on the IBM web site?

 

 

[Khai Nguyen]

Hi,

Thanks for the attention to my problem.

I would like to provide more necessary information:
- IBM Storage FS5035 firmware: Version 8.4.0.4 (build 152.24.2109140942000)

- HBA FC Card: Lenovo Emulex 01CV842 16GB FC Dual-port HBA - FC ( P/N: 01CV842, firmware version 11.4.168.8)

- Physical Server:Rack server ProLiant DL380 Gen10 (6.7.0 build-17167734)

- The connection between the Server and the Storage use FC Switch: Cisco MDS 9148S 16G Multilayer Fabric Switch ( P/N: DS-C9148S-K09 V01 )

- I recheck the compatible from SSIC IBM and Some things are not compatible. But i have the same server ProLiant DL380 Gen10 with similar connection and everything is stable. I have deployed a lot of SAN FS5000 with ESXi server and many cases do not meet the full compatibility of FC Switch, HBA card, Physical Host from SSIC but no error occurs. I think SSIC doesn't show all compatible components.

I hope you can answer my problem. I hope this is just a display error and does not affect system operation.

Thanks

 

[Khai Nguyen]

Sorry Sir,
I have some mistake about the information:
- HBA FC Card: Emulex 01CV842 16GB FC Dual-port HBA 

 +P/N: 01CV842

 +Model:  LPe31002-M6-L

 + firmware version 11.4.168.8

So I recheck the compatible and everythings validated on SSIC IBM

 

[E_Espinel]

Hello.
The levels and combinations presented by IBM SSIC and VMware matrix compatibility are generally the minimum recommended and/or tested. You have to consider that they are continuously updated.

The Luns that appear as not consumed have the same type of disks as the other luns (SSD)?

from an ssh connection to the ESXi host run the following command

esxcli Storage Core path list

and verify that you see the same amount and the same number of luns that are received from storage.

 

 

[Khai Nguyen]

Hi Sir,

More information for you:
- The Luns that appear as not consumed have the same type of disks as the other luns, you can see on pictures below: LUN 4 5 6 7 have the same type of disks

- And here is the datastorage after rescan a few times. Additionally, I use increase datastorage to merge 4 luns together, and 4 volume have created on Data redution pool with type compressed volume.

- I run command "esxcli Storage Core path list",  the same amount and the same number of luns that are received from storage.

fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000016
UID: fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000016
Runtime Name: vmhba2:C0:T4:L4
Device: naa.600507638081065ed000000000000016
Device Display Name: IBM Fibre Channel Disk (naa.600507638081065ed000000000000016)
Adapter: vmhba2
Channel: 0
Target: 4
LUN: 4
Plugin: NMP
State: active
Transport: fc
Adapter Identifier: fc.200000109bc4b819:100000109bc4b819
Target Identifier: fc.500507680d0263a3:500507680d7a63a3
Adapter Transport Details: WWNN: 20:00:00:10:9b:c4:b8:19 WWPN: 10:00:00:10:9b:c4:b8:19
Target Transport Details: WWNN: 50:05:07:68:0d:02:63:a3 WWPN: 50:05:07:68:0d:7a:63:a3
Maximum IO Size: 33553920

fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000017
UID: fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000017
Runtime Name: vmhba2:C0:T4:L5
Device: naa.600507638081065ed000000000000017
Device Display Name: IBM Fibre Channel Disk (naa.600507638081065ed000000000000017)
Adapter: vmhba2
Channel: 0
Target: 4
LUN: 5
Plugin: NMP
State: active
Transport: fc
Adapter Identifier: fc.200000109bc4b819:100000109bc4b819
Target Identifier: fc.500507680d0263a3:500507680d7a63a3
Adapter Transport Details: WWNN: 20:00:00:10:9b:c4:b8:19 WWPN: 10:00:00:10:9b:c4:b8:19
Target Transport Details: WWNN: 50:05:07:68:0d:02:63:a3 WWPN: 50:05:07:68:0d:7a:63:a3
Maximum IO Size: 33553920

fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000018
UID: fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000018
Runtime Name: vmhba2:C0:T4:L6
Device: naa.600507638081065ed000000000000018
Device Display Name: IBM Fibre Channel Disk (naa.600507638081065ed000000000000018)
Adapter: vmhba2
Channel: 0
Target: 4
LUN: 6
Plugin: NMP
State: active
Transport: fc
Adapter Identifier: fc.200000109bc4b819:100000109bc4b819
Target Identifier: fc.500507680d0263a3:500507680d7a63a3
Adapter Transport Details: WWNN: 20:00:00:10:9b:c4:b8:19 WWPN: 10:00:00:10:9b:c4:b8:19
Target Transport Details: WWNN: 50:05:07:68:0d:02:63:a3 WWPN: 50:05:07:68:0d:7a:63:a3
Maximum IO Size: 33553920

fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000019
UID: fc.200000109bc4b819:100000109bc4b819-fc.500507680d0263a3:500507680d7a63a3-naa.600507638081065ed000000000000019
Runtime Name: vmhba2:C0:T4:L7
Device: naa.600507638081065ed000000000000019
Device Display Name: IBM Fibre Channel Disk (naa.600507638081065ed000000000000019)
Adapter: vmhba2
Channel: 0
Target: 4
LUN: 7
Plugin: NMP
State: active
Transport: fc
Adapter Identifier: fc.200000109bc4b819:100000109bc4b819
Target Identifier: fc.500507680d0263a3:500507680d7a63a3
Adapter Transport Details: WWNN: 20:00:00:10:9b:c4:b8:19 WWPN: 10:00:00:10:9b:c4:b8:19
Target Transport Details: WWNN: 50:05:07:68:0d:02:63:a3 WWPN: 50:05:07:68:0d:7a:63:a3
Maximum IO Size: 33553920

- Btw, It's been a few days since the datastorage stopped showing the not consumed error. I'm afraid it will fail again and affect the system.

[mbufkin]

I have the same model IBM Storage connected to a Cisco UCS Blade system with Cisco MDS switches. I have not seen this issue but will be monitoring this thread for a solution.

[Akin Akalan]

so not consumed means its not recognized as a datastore.

Are you sure these are datastores? It maybe a RDM disks?

can you check other hosts with the same naa id?