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

0 Kudos
48 Replies
tranminhsam2018
Contributor
Contributor
Jump to solution

It still the same. Nothing change. I removed an old server and replace by this.

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

My first message on this topic. Figure 3 please review you will see it.

0 Kudos
SupreetK
Commander
Commander
Jump to solution

Let me try to understand this. According to your observation, the port state still shows as blocked even if a working 6.0 host is connected to the controller port to which the 6.7 host is connected currently? If yes, then I don't think it is a problem with ESXi.

Cheers,

Supreet

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Actually like this.

- We have 1 SAN and 4 Servers (IBM X3650 direct connection, we do not have the san switch).

- After that, we bought a new server (Lenovo Thinksystem Sr650). We removed an old server and replace it by this new server. Of course, the new server will use the port (SAN) of the old server. On the SAN, we reconnect the hba port of the new server (figure 1+2).

- With old server (IBM x3650) use same port on SAN (of new Server) can connect and use normally (figure 3);

- Working with netapp engineers we have tried all of these options.

3.jpg

1.jpg

11.png

0 Kudos
SupreetK
Commander
Commander
Jump to solution

Can you try a adapter reset from our side?

esxcli storage san fc reset -A vmhba2

esxcli storage san fc reset -A vmhba3

Cheers,

Supreet

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Hi Supreet.

- After using your command with vmhba2, I see the port is open state  (Have a little hope.. pls see figure 1)

- But using your command with vmhba3, port is still closed.

- I restarted esxi and tried again many times. Now ports 2, 3 are closed (It no longer works. Only works for the first time with vmhba2)

I do not understand why.

12.jpg

13.png

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

.. Next i do so:

- Re-install esxi still that version.

- And run your command (esxcli storage san fc reset -A vmhba2 & esxcli storage san fc reset -A vmhba3)

- Same as previous times... only vmhba2 was open (figure 1).

--> single port open vmhba2 (vmhba3 still closed) not enough to access.

--> When I run your commands again one more time.... all will disappear. Everything goes back to the original (see final image)

----> I can conclude drive FC has problems.

13.png

14.png

15.png

16.png

17.png

18.png

0 Kudos
SupreetK
Commander
Commander
Jump to solution

Looks like we are dealing with faulty HBAs. Before concluding, can you try installing 6.0 U3 and check the status?

Cheers,

Supreet

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

As your request.

1.png

2.png

3.png

4.png5.png

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

... And after run your command. No changes.

6.png

7.png

8.png

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

9.png

0 Kudos
SupreetK
Commander
Commander
Jump to solution

Great! Looks like we are dealing with faulty HBAs or a bad physical connection. The status is the same on both 6.0 and 6.5.

Cheers,

Supreet

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

but still with this port if use ibm x3650 server will not matter.

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

So wait for the new adater driver.

0 Kudos
SupreetK
Commander
Commander
Jump to solution

Primarily, there are four common things here -

1) ESXi OS

2) HBA

3) Cable

4) Port on the controller

Since the same port and cable are working well with a different model of HBA and ESXi, don't think it is a problem with either.

Therefore, it has to be something with the HBA and its driver/firmware compatibility with the ESXi. Now that we have tried a various combinations of driver/firmware and ESXi, we can rule this one out as well. So it has to be something with the HBA.

Cheers,

Supreet

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

If I remove this new server out and replace it by the old server it works normally (same cable and port on SAN). We are using the same before having a new server. Only that can be

1. Esxi

2. Hba

0 Kudos
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

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

I agree completely with you. I do not know what to do next...? And thanks you so much Supreet.

0 Kudos
SupreetK
Commander
Commander
Jump to solution

Please open up a support ticket with Lenovo and one with VMware if, Lenovo requests for it.

Cheers,

Supreet

0 Kudos
tranminhsam2018
Contributor
Contributor
Jump to solution

Sorry, I did that but they just want to sell.

0 Kudos