- Why did HP Create Virtual Connect? ( define the business problems)
- Physical – Too many Cable or Too many switches
- Organizational – 3 teams managing one blade enclosure
- Agility & resiliency – Separate workload from physical server
mezzanine card = blade
What is Virtual Connect? Whatís needed to use it?
- two minutes on virtual network adapters and how it impacts server and network design.
History of Virtual Connect
- 10Gb w/Flex-10
- FCoE – FlexFabric
Whatís Good About Virtual Connect ?
- Fit into any environment
- Reduce cables without adding ìswitchesî
- Enable stateless servers
- Bridge between Server team & LAN/SAN teams
Whatís the difference between Flex-10, FlexFabric, etc etc.
How to understand the differences, because I find the plethora of products to be confusing and a lot of the terminology drives me mad.
Links to relevant HP documenation
In addition to full iSCSI offload, the Virtual Connect FlexFabric module supports and manages iSCSI boot. The iSCSI boot parameters can be managed as part of the Virtual Connect server profile, creating a stateless server using a cost effective iSCSI boot device. This capability was only available on Native Fibre Channel in previous versions of Virtual Connect, now itís available on all storage protocols supported by the Virtual Connect FlexFabric module; Fibre Channel, FCoE and iSCSI. Much as I’m confused by Virtual Connect for its complexity and stupid design parameters, at least they have delivered a viable iSCSI solution for blade / chassis servers. Iíll be taking a closer look at this.
Subscribe in iTunes and RSS
Media Player and MP3 Download
You can subscribe to the RSS feed or head over to the Packet Pushers website to download the MP3 file directly from the blog post for that episode. Also, subscription options for Zune, Boxee and a range of other podcatchers are listed on the website.