VMware Cloud Community
tranminhsam2018
Contributor
Contributor
Jump to solution

In Esxi 6.7 - (HBA) SAN FC showing as Blocked Port.

Hi All.

I need your help. Thinksys sr650 direct connections (FC) with Netapp E2724.The SAN partition is not displayed. I can see new ESXi connected to Controller A port  5 and Controller B port 4. In storage end these ports are up. When i run the command "esxcli storage san fc list " --> Error message is : "Port State: BLOCKED".

block port.png

Reply
0 Kudos
1 Solution

Accepted Solutions
SupreetK
Commander
Commander
Jump to solution

Exactly, that is what even I am saying Smiley Happy Since the new server has been tried with both 6.7 and 6.0 version (and a various combination of driver/firmware for the HBA), most likely it is not an issue with ESXi. Culprit could be the HBA cards.

Cheers,

Supreet

View solution in original post

Reply
0 Kudos
48 Replies
GayathriS
Expert
Expert
Jump to solution

Hi Could you please confirm the make and model of of storage that you are using : from your question I see 2 things mentioned as Thinksys sr650 and Netapp E2724

This is your storage make and model : Netapp E2724  ?

Because I dont see this model in the compatibility guide .

VMware Compatibility Guide - Storage/SAN Search

Am I missing anything here , Could you please confirm on this .

regards

Gayathri

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Hi Gayathri.

we are using Lenovo Thinksystem Sr650 and SAN (Netapp E2724 - E2700 Data Storage System – Hybrid Storage Solutions | NetApp ).

Reply
0 Kudos
Ganeshpal
Enthusiast
Enthusiast
Jump to solution

Hi Tran,

Have given proper zoning permission to storage level or SAN Switch level.

Thanks and Regards,

Ganeshprasad Pal    

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Hi Ganeshprasad

From server (esxi) direct connections to San (Netapp). We not use san switch.

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

I don't think all the FC arrays support direct connections from the ESXi hosts. If they do support, some additional configuration might be involved. You might want to post this query on the NetApp community as well -

VMware Compatibility Guide - Storage/SAN Search

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

Cheers,

Supreet

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Hi Supreet.

No problem with 3 servers (Ibm x3650 - esxi 6.0) that are connected directly for 4 years. We only have problem with esxi 6.7 (thinksystem sr 650).

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Hi All.

I want to update more data, We have worked with netapp engineers.

"

Controller A Port5

===============

Host interface: Fibre

Host Interface Card(HIC):     1

Channel: 5

Port: 5

Current ID: Not applicable/0xFFFFFFFF

Preferred ID: 4/0xE1

NL-Port ID: 0x000000

Maximum data rate:            16 Gbps

Current data rate: 16 Gbps

Data rate control:            Auto

Link status: Up

Topology: Point-to-Point

World-wide port identifier:   20:52:00:a0:98:65:5f:8f

World-wide node identifier:   20:02:00:a0:98:65:5f:8f

Part type: QL-EP8324           revision 2

Data Assurance (DA) capable:  Yes

Date/Time: 8/16/18 4:44:52 PM

Sequence number: 64514

Event type: 1018

Event category: Internal

Priority: Informational

Event needs attention: false

Event send alert: false

Event visibility: true

Description: Fibre channel link up

Event specific codes: 0/0/0

Component type: Channel

Component location: Host-side: controller in slot A, port 5

Logged by: Controller in slot A

Controller B Port4

===============

From events:

Host interface: Fibre

Host Interface Card(HIC):     1

Channel: 4

Port: 4

Current ID: Not applicable/0xFFFFFFFF

Preferred ID: 13/0xD2

NL-Port ID: 0x000000

Maximum data rate:            16 Gbps

Current data rate:            16 Gbps

Data rate control:            Auto

Link status: Up

Topology: Point-to-Point

World-wide port identifier:   20:43:00:a0:98:65:5f:8f

World-wide node identifier:   20:02:00:a0:98:65:5f:8f

Part type: QL-EP8324           revision 2

Data Assurance (DA) capable:  Yes

Date/Time: 8/16/18 4:40:05 PM

Sequence number: 64506

Event type: 1018

Event category: Internal

Priority: Informational

Event needs attention: false

Event send alert: false

Event visibility: true

Description: Fibre channel link up

Event specific codes: 0/0/0

Component type: Channel

Component location: Host-side: controller in slot B, port 4

Logged by: Controller in slot B

ESXi port status:

[root@localhost:~] esxcli storage san fc list

   Adapter: vmhba2

   Port ID: 000000

   Node Name: 20:00:00:10:9b:3b:81:be

   Port Name: 10:00:00:10:9b:3b:81:be

   Speed: 16 Gbps

   Port Type: PTP

   Port State: BLOCKED

   Model Description: Emulex 01CV842 16Gb FC Dual-port HBA

   Hardware Version: 0000000c

   OptionROM Version: 11.4.168.16

   Firmware Version: 11.4.168.16

   Driver Name: lpfc

   DriverVersion: 12.0.193.14

   Adapter: vmhba3

   Port ID: 000000

   Node Name: 20:00:00:10:9b:3b:81:bf

   Port Name: 10:00:00:10:9b:3b:81:bf

   Speed: 16 Gbps

   Port Type: PTP

   Port State: BLOCKED

   Model Description: Emulex 01CV842 16Gb FC Dual-port HBA

   Hardware Version: 0000000c

   OptionROM Version: 11.4.168.16

   Firmware Version: 11.4.168.16

   Driver Name: lpfc

   DriverVersion: 12.0.193.14

"

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

Are the x3650 servers using the same model HBA? Can you run the command <vmkchdev -l | grep -i vmhba2> on the SR650 and share the output?

Cheers,

Supreet

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Hi Supreet.

HBA for the new server can not be the same old server. Ibm x3650 Mxxx serial is a very old server line of ibm and Thinksystem Sr650 is very new line (different architectures altogether.)

5.png

6.png

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

Looks like both driver and firmware are on an unsupported version. They are not even listed in the VMware HCL. You might want to upgrade them to the latest version (Though I'm not sure if this is the cause) -

VMware Compatibility Guide - I/O Device Search

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

Cheers,

Supreet

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

According to my search the final version has been updated (esxi 6.7 and Emulex 01CV842 16Gb FC Dual-port HBA 11.4.168.16). I also tried other versions without results.

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

Did you try the latest driver and firmware version listed in the above VMware HCL link?

Cheers,

Supreet

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Iam using this version and other versions have tried to install. Please see the two images below.

7.png

8.png

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

If you check the HCL link which I shared in my previous reply, only below driver and firmware versions are supported -

pastedImage_0.png

I would suggest upgrading to the driver version 12.0.257.5 and firmware version 12.0.257.5 (or above).

Cheers,

Supreet

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

I installed it, still can not see san partition.

9.png

10.png

11.png

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

I can not find the firmware version 12.0.257.5 ; can only upgrade DriverVersion: 12.0.257.5

pastedImage_1.png

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

Even I'm unable to locate the download link for the firmware version '12.0.257.5'. Looks like there is a discrepancy in the data on the HCL Smiley Sad To isolate if there is any issue at the hardware layer, can you swap the ports between one working 6.0 host and one 6.7 host? For e.g. if HBA of the working 6.0 host is connected to controller port-1 and the HBA of 6.7 host is connected to controller port-2, unplug and connect 6.7 HBA to port-1 and 6.0 HBA to port-2. You might have to reconfigure the presentation based on the change in the WWN. Post performing this swapping, reboot both 6.0 and 6.7 hosts and check the port status.

Cheers,

Supreet

Reply
0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

I did that before (many times).. but no results.

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

If you connect a 6.0 host to the 6.7 connected controller port, what is the status of the port? Does it stay as blocked or does it show active?

Cheers,

Supreet

Reply
0 Kudos