Found this great document for those who want to start implementing Virtual Connect Enterprise Manager... Happy reading and/or installing!
I got some questions regarding adding additional NICs in the P4000 storage nodes... Find here the doc that explains everything...
This paper compares the network architecture, configuration, deployment, management capabilities, and performance of two systems: • HP BladeSystem servers with Virtual Connect (VC) •
Distributed Trunking is a link aggregation technique, where two or more links across two switches are aggregated together to form a trunk. The IEEE
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdf Introduction HP provides technologies and tools for efficiently managing Virtual Connect (VC) environments of all sizes. HP Virtual Connect Manager (VCM) is a
ProCurve / Cisco Interoperability Guide : PDF ProCurve & Cisco Spanning Tree Interoperability : PDF
HP just announced Virtual Connect Firmware version 3.30. Following are the select new features supported in VC 3.30 including many others. For details please refer to
This new guide provides detailed design scenarios, configuration examples, and best practices for an Intelligent Resilient Fabric (IRF) environment with Virtual Connect and HP
The HP Virtual Connect FIbre Channel Scenarios Cookbook has been updated! Check it out!! http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01702940/c01702940.pdf
Q.) I know that when not defining an uplink port, either directly or via a SUS, that traffic will stay within the VC domain.