- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- VMWare: Lost SCSI reservations can occur when usin...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2010 08:20 AM
11-17-2010 08:20 AM
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.
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?