Skip to main content

Posts

Showing posts from June, 2013

All paths lost on HBA port

HP, a great company, I like the hardware design of HP ProLiant server, it's pretty easy for datacenter maintenance and operation, do you like it? Today, I'll introduce a storage issue on HP ProLiant BL460, BL480 blades. This issue happened on Qlogic HBA with VC-FC module. I have two dual port Qlogic HBAs on each ESXi5.x host, one port of each HBA was zoned together on SAN switch. For example, vmhba1 and vmhba3 are zoned for LUN allocation, each LUN have two paths on each HBA port. I observed all LUNs disappeared on random HBA port sometimes, it's not happening very frequently, but it can lead to ALL VM DEAD if you get storage outage when LUNs disappeared!!! This problem becomes more frequently more your virtual infrastructure grows bigger. This is the symptoms when the issue happening: And if you login SSH console and check HBA card status by: less /proc/scsi/qla2xxx/[ Device ID ] You will find following differences of two HBA ports: See? All targets show Offline status o

vCenter Server Heartbeat 5.6 - Architecture

I start to use VMware workstation since 2002 or earlier, my bad memory can't recall it. That's 1 st generation of virtualization. If you look at today's virtual world, we are on the way to "Matrix"! J Enterprise is virtualizing more and more server lead to vCenter Server becomes to a critical role. We have to prepare for any contingency. vCenter Server Heartbeat (vCHB) is a nice candidate for protecting vCenter Server. It provides your infrastructure ability to prevent downtime/outage of vCenter Server. To gearing up for implementation in production environment, I did some testing on my LAB, the product is nice, but the document is not ideal. I'd like to share my experience, this blog also referred to my project document, please let me know if you have any idea can help me make my document ideally. Thanks in advance. vCHB is a cluster service like Microsoft Cluster Service or any other 3 rd part cluster software. The benefit of this product is you don'

A disk read error occurred after upgrade HW version from 3 to 9

This was a lesson and learns for me after I recovered the data back. My data was lost and no backup… I had a virtual machine was moved from ESX 3.0 to ESXi 5.1 host long time ago. The virtual disk size show 0 and I cannot do storage migration and snapshot on the VM due to the hardware version was 3, it's too low. Generally I take snapshot before upgrade VM HW version, but that's impossible on a VM of HW version 3 that running on vCenter Server 5.1. So I upgraded the VMware Tools and then VM hardware version by Update Manager. VMware Tools was successfully upgraded, but VM hardware version upgrading got error. Then I right clicked the VM and used " Upgrade Hardware Version" option directly, it's successfully without any prompt…finally I got " A disk read error occurred " when boot up. L You may think it's caused by SCSI controller since VM hardware version 3 supports IDE virtual disk and version 9 supports only SCSI virtual disk for best performance