VMware Cloud Community
VirtualAerospac
Contributor
Contributor
Jump to solution

HBA Status Dead

Hello,

We have recently upgraded our Vmware infrastructure to 4.1. We have moved our 12 hosts and the VMs to vSphere Client 4.1 and so far 3 of our hosts are up to 4.1, the rest will be done over the week ahead.

Everything is working fine and having no issues.

Looking more into it I noticed something under Configuration/Storage Adapters. We have 2 PCI Express HBA cards listed there for each host.

When we click on Vmhba2 then paths the status is all Active (green)

When we click on Vmhba1 then paths the status should say standby but coming back as dead

I have tried to find anything out I can on Google but having no such luck.

So I have turned again to VMware Communities site for help.

I have attached screenshots of it

If you need any other information please let me know

(hope any of it makes sense)

Thanks.

Austin.

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
PUREJOY
Enthusiast
Enthusiast
Jump to solution

Try rescan all under the configuration --> storage tab

Sometime the vcenter paths doesn't reflect the current state. I have seen this before. After rescanning, if all things are configured correctly (best to check SAN Switch zoning, connectivity status,...) you shoudl get back your path.

Just to confirm this, can you run

esxcfg-mpath -l | grep -i State| grep -i dead

you shouldn't see any dead path, if you see then you are seeing a real problem.

Then you have to go back and see the end to end connectivity status.

Architect @ Pure Storage || www.purestorage.com || http://www.purestorage.com/blog/ || http://twitter.com/#!/purestorage ||@ravivenk || VCAP-DCA5, VCP 4, VCP 5

View solution in original post

Reply
0 Kudos
6 Replies
Troy_Clavell
Immortal
Immortal
Jump to solution

Are you connecting to a SAN Switch?  Maybe a bad GBIC?  You may want to talk to your Storage folks to figure out what's going on.  I don't believe this is an ESX(i) issue

VirtualAerospac
Contributor
Contributor
Jump to solution

Yes we are connecting to a san switch.

I have talked with storage and everything is fine - I was just curious as to anyone seen or had an issue like this

Could it maybe something in the configuration on VI client

Thanks for the response.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal
Jump to solution

I don't believe it's a configuration issue on your end.  The paths are being seen, but just as dead.  Those are valid targets on your SAN correct?  Have you tried rescanning your storage adapters?

the KB article below may or may not be relevant but, just in case

http://kb.vmware.com/kb/1010570

PUREJOY
Enthusiast
Enthusiast
Jump to solution

Try rescan all under the configuration --> storage tab

Sometime the vcenter paths doesn't reflect the current state. I have seen this before. After rescanning, if all things are configured correctly (best to check SAN Switch zoning, connectivity status,...) you shoudl get back your path.

Just to confirm this, can you run

esxcfg-mpath -l | grep -i State| grep -i dead

you shouldn't see any dead path, if you see then you are seeing a real problem.

Then you have to go back and see the end to end connectivity status.

Architect @ Pure Storage || www.purestorage.com || http://www.purestorage.com/blog/ || http://twitter.com/#!/purestorage ||@ravivenk || VCAP-DCA5, VCP 4, VCP 5
Reply
0 Kudos
Rubeck
Virtuoso
Virtuoso
Jump to solution

Yes, I've seen this before.... This was due to a bad GBIC, as mentioned above.. 

Checking the loop state in /proc/scsi/qlaxxx/<portnumber> show'ed that the loop was down... So it had to be either the FC cable or a faulty GBIC as nothing had been changed in the fabrics or SAN.. 

/Rubeck

Reply
0 Kudos
VirtualAerospac
Contributor
Contributor
Jump to solution

Thanks for the help guys! Going to be trying it today and see how it turns out

Many thanks

Reply
0 Kudos