Forum Discussion
Abed_AL-R_26070
Nimbostratus
NimbostratusF5 failover traffic
Hi
We have F5 machine connected to one backbone switch.
We're going to configure another backbone switch in case the first one went down.
How can we configure in the F5 two interfaces in case t...
eben_259100
Cirrostratus
Cirrostratus
Abed_AL-RThank you, But I got lost in that document :) There is too much information for my little question Any specific direction and direct to the point ? Thanks
- eben_259100
what kind of core switch is it? have you worked with Virtual Port Channel on a nexus switch?
- Abed_AL-R
Juniper EX4550
- eben_259100
what is your current connection like? F5 -> ex4550? what will the connection be like when the new ex4550 is deployed? ex4550_1 -> ex4550_2
- Abed_AL-R
Today there is two LACP connections going directly from f5 to ex4550_1 (VisrtualChassis) (3/1.1 and 3/1.4) The f5 machine is in cluster mode (2 nodes active-passive) We're are going to add another ex4550_2 (VirtualChassis) and connect the both nodes of f5 machine to both ex4550_1 and ex4550_2 machines Today, on each f5 machine we have another two free links which we want to use for the new deployment
- eben_259100
- f5(interface1) -> ex4500_1
- f5(interface2) -> ex4500_2 This should be your lacp links. if your config(VirtualChassis) is fine on the ex4500, F5 should see this connection like its connecting to one device. so if ex4500_1 goes down, ex4500_2 continues to forward traffic. Note: You have to split existing LACP connections to both ex4500s for failover to work.