HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

VMWare: Lost SCSI reservations can occur when using HP Blades and the Virtual Connect Module

 
chuckk281
Trusted Contributor

VMWare: Lost SCSI reservations can occur when using HP Blades and the Virtual Connect Module

Lawrance provided some VMware info:

 

*******************

 

Found a VMware support document that mentions VMWare having a requirement for a minimum Virtual Connect Fibre Channel firmware version, which I thought could be interesting for those of us who have customers running VMware on c-Class blade servers with Virtual Connect.

 

http://kb.vmware.com/selfservice/microsites/microsite.do?cmd=displayKC&docType=kc&externalId=1029485&sliceId=1&docTypeID=DT_KB_1_1

 

From what I have understood of that document, basically if your customer is running VMware on servers that are in a c Class blade enclosure that has virtual connect fibre channel modules, they need to be on VC Ethernet 3.xx code, instead of 2.xx code.

 

VC firmware 2.30, 2.31, 2.32, 2.33, 3.01 and 3.10 include VC-FC firmware 1.40.   Which is what the document states is a minimum requirement.

 

VC firmware 1.34, 2.02, 2.10 includes VC-FC firmware 1.3x so it’s a definite no-no.

 

The very latest VC firmware 3.15 and 2.34 includes VC-FC firmware 1.41 which exceeds the minimum requirement.

 

*****************************

 

Any commnets or questions?