For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Josh_41258's avatar
Josh_41258
Icon for Nimbostratus rankNimbostratus
Jun 17, 2014

vCMP Failover Scenarios

Let's say I have (2) C2400 chassis with (2) B2100's installed in each. Network connections are as follows: C2400-01/Slot1 - Connected to Switch_1 C2400-01/Slot2 - Connected to Switch_2 C2400-02/S...
design
vcmp
Josh_41258's avatar
Josh_41258
Icon for Nimbostratus rankNimbostratus
Jun 18, 2014

Thanks for the diagram. I believe I am going to end up having one VPC per chassis and multi-homing each blade to both N7K's. Prior to this design, I had separate physical interfaces (and VPCs) for internal and external traffic. I am now contemplating consolidating these into the same physical interfaces and VPCs which will free up the additional 10GB interfaces on the N7K's that I need for multihoming each blade.

 

Each connected interface on the chassis will be a member of the same trunk. Aggregate bandwidth available to the trunk will of course be determined by the number of physical interfaces spanning the blades of the entire chassis (2 blades = 40Gbps, etc).

 

This will provide switch redundancy for even the LTM instances that only span one blade since each blade will be connected to both N7K's.

 

Steve_M__153836's avatar
Steve_M__153836
Icon for Nimbostratus rankNimbostratus
Jun 18, 2014
That sounds like a good plan. It is nice with the vCMP functionality that you can trunk all the VLANs you want over one vPC and then decide what LTM instance gets what VLAN. This devcentral thread(https://devcentral.f5.com/s/feed/0D51T00006i7MMdSAM) has a very useful piece of info at the end of it regarding what you name your vPC and how it is configured on the F5 (names must match).