This article is moved towards my new site:
« Creating easy to identify LeftHand Volumes on ESX/vSphere
VMware vCenter Storage Views: Partial/No Redundancy »
[…] Update 04-12-2009: Since this post is one of my top articles I decided to write more about the extensive testing, read all about it here […]
[…] – vcutil 24 12 2009 After rebooting several Virtual Connect Modules to test the failover behaviors I got myself in a situation in were the Virtual Connect Manager got completely unresponsive. In my […]
Kenneth – another great job. You’ve enlightened me with some info that I was not aware of with the Flex-10 switches. Your idea of connecting IC’s 1 and 2 to 5 and 6 via the CX4 cable is a good idea, but I’d be curious as to if there are any performance hits. The design appears to offer 4 x FlexNICs (2 onboard and 2 via the mezzanine) – is this to help provide ESX with the quantity of vNICs it needs?
The connection between IC modules (horizontal) is done via the c7000 midplane, so that’s like default.
The connection via CX4 is done as described by HP so this is mandatory as well. The total number of FlexNics in this configuration is 16 which gives you several options to configure a design.
Maybe I’m missing something but stacking links aren’t mandatory. Why did you use them?
You are correct, I mentioned that the stacking cables are mandatory but they aren’t.
The are however recommended and offer you redundancy whenever one of the VC modules fails.
You can read more about these stacking cables over in the HP Virtual Connect for c-Class BaldeSystem Setup and Installation Guide (starting from page 53)
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of new comments via email.