HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

Virtual Connect Cabling Question

 
Allan Zawadowicz
Occasional Visitor

Virtual Connect Cabling Question

We are considering purchasing a C class chassis with VC Flex 10 modules. Then connecting each VC mod to 2 separate 6509s with 6708 modules. How many cables are required for the uplinks? 2 for each side, a total of 4? In what way do the 6509s need to be linked? Is the bonded 2 Gig link between the supervisor modules enough?
2 REPLIES
HEM_2
Honored Contributor

Re: Virtual Connect Cabling Question

There really is no minimum requirement for cabling VC to your external switches. You obviously at least need one uplink for any connectivity whatsoever and probably 2 (1 per bay) for redundancy. The rest is dictated by the bandwidth needs you have. 2 uplinks per bay for a total of 4 uplinks give you a potential of 40Gb of bandwidth when employing an Active/Active VC uplink configuration.

As far as the 2 Gb inter-switch-link for your 6509's... once again it depends on how your traffic will flow. If the VC traffic must flow over the 2Gb link to get to its destination then it could be considered a bottleneck.

HTH
Allan Zawadowicz
Occasional Visitor

Re: Virtual Connect Cabling Question

Hmmm....I was told you need to reserve 2 ports on the 6708 and only on one side for lag. But not really sure what that means. Any idea?

I agree with the 2 gig link being a bottleneck. Our secondary core is mostly idle because of spanning tree blocks. So right now that link is mostly unused. If our primary core failed, the secondary core would provide connectivity to the distribution and access switches.