On Monday, April 20th, we announced a new Virtual Connect family member and expanded capabilities for all Virtual Connect products. We’ve see a great deal of momentum building behind virtualization and infrastructure convergence - and these enhancements will help our customers better meet their goals.
When customers put applications onto fewer servers with virtualization, they increase the needed density of both data and storage networking. So, customers not only need server virtualization, but they also need to virtualize and converge server I/O. Last November, we introduced the HP Virtual Connect Flex-10 technology that divides a dual-port network interface controller into 8 FlexNIC ports. This technology reduces the cost associated with data networking in a virtualization environment by greatly reducing the number of cables, switches and additional NICs needed.
Now we just announced a new Virtual Connect 8 Gb Fibre Channel module to support the heavy SAN needs of virtual servers. The HP Virtual Connect 8 Gb 24-port Fibre Channel Module has twice the bandwidth of our 4 Gb Fibre Channel module running at up to 8 Gb on all downlinks and uplinks. Second, it has a total of 8 uplink connections, which is double our current module. Third, it features support for increased server side NPIV support with 255 World Wide Names available per server. So all together more Virtual Machines can be hosted per server and per set of Virtual Connect Ethernet and Fibre Channel modules. The result is needing fewer servers AND fewer interconnect modules. Fewer servers and interconnect modules mean a lower purchase cost, simpler set-up and ongoing management, and fewer cables, all able to host more application workloads.. More for less works well for everyone.
We added a new Virtual Connect multi-enclosure stacking feature. Multi-enclosure stacking allows up to 4 BladeSystem enclosures to be connected together into one Virtual Connect Domain. This provides two big benefits. One, it creates a single simple server connection management domain for up to four enclosures, or up to 64 servers. Second, it also means fewer uplink cables to top of rack or core network ports, further reducing cable and expensive core port costs.
We’ve also enhanced Virtual Connect Enterprise Manager. The new 1.30 release supports our new Virtual Connect 8Gb Fibre Channel Module, our latest G6 server blades announced last month, and extends the number of supported Virtual Connect domains to 200. When combined with multi-enclosure stacking, this means that Virtual Connect Enterprise Manager can simplify the set-up and ongoing management of server I/O for up to 800 BladeSystem enclosures or put another way, up to 12,800 servers! Enabling system administrators the ability to manage the connectivity of up to 12,800 servers will go a long way to making life simpler and less expensive for many of our customers.
So for customers looking to converge infrastructure or increase benefits from virtualization, we hope you let HP and our resellers help you save money, reduce your network complexity, and simplify your IT environment with Virtual Connect Ethernet and Virtual Connect Fibre Channel.
“Connect More - Spend Less!”
ESS Virtual Connect
This one of the methods used to provide fail over for network traffic.
From our BladeSystem support staff
"This is just a “redundancy mechanism” that is part of the HP Teaming driver.Not trying to over simply things but here it goes. NIC A and NIC B are teamed together. NIC A is receiving frames okay, NIC B has not received any frames.Teaming driver sends “Test Frame” out NIC A, sets timers and waits for NIC B to receive it. This is repeated a few times.If NIC B still has not received a frame after a few intervals, it is determined the RX (Receive) Path to this NIC is broken, thus NIC is marked as “Receive Path Validation” and is removed as an Active member of the team. This is a good thing because we don’t want a NIC in the team that can’t hear… So…either there is a problem with that NIC receiving frames (fix it) or there is a problem in the Teaming driver detecting “false” RX Path failures.Either way the recommendation is never to disable it as a solution to the problem.