NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Link redundancy
Hello, I have an hp switch (Core switch) connected to two M4300 switches both connected to each other again and i want to establish failover/link redundancy between the switches. Not sure if LAG...
Hello schumaku
Thanks for your response.
The task is still pending.
The two switches are not stacked and i have two direct link to the switches however i want to configure such that when a link fails the other comes up and could be an uplink to the other switch also
I have tried to configure a dedicated trunk containing multiple links LACP in both ends of the trunk. Instead of providing link redundancy it creates loop.
What am i not doing right?
Looks like there is some confusion.
Each LAG (assume you have multiple physical links between the three switches) must be configured individually, e.g. you can't define a single LAG on the HPE switch and then connect both standalone Netgear switches.
Of course, to avoid a loop between the three switches is predictable, the minimum you can do is to establish an appropriate spanning tree config, with meaningful priorities set for each LAG. Yes, in an STP (better start with RSTP to avoid a to long waiting time after booting or connecting the switches).
Yes, STP and RSTP will take down a lower prioritized connection, e.g. the one between the two Netgear edge switches, where you might want the LAGs to the core switch keeping priority.
Can you give a diagramatic illustration to this please?
I need help getting the core switch and the distribution switches to have failover and redundancy
I am also option to other options and recommendations
What I have in mind are LAGs "A", "B", and "C", each independent -. mixing LAG configs and connections won't be correct.
With STP resp. RSTP, one of the LAGs will have to be automatically disabled, to avoid a loop condition.
The math of costs is explained in https://en.wikipedia.org/wiki/Spanning_Tree_Protocol
Of course you can consider some more sophisticated solutions, like additional LAGs between the three switches, so up to five are possible - depending on your operational requirements - that would require looking into MSTP.
Regards,
-Kurt.
This is great.
I would require assistance configuring LAG on these three
Just a look through about the script to achieve this
# # On SWITCH A-Enable RSTP globally
[HP5500] stp mode rstp## On SWITCH A-Create LAG 1 for Switch
interface lag 1
description "LAG to Switch B/C"
no shutdown
switchport mode trunk
switchport trunk allowed vlan 1,10,15,25,30-32,40,50-51,60,70,99-100,160,200,999
exit! Assign ports 1/0/19 and 1/0/20 to LAG 1
interface 1/0/19
description "LAG member to Switch B/C"
channel-group 1 mode on
exitinterface 1/0/20
description "LAG member to Switch B/C"
channel-group 1 mode on
exit# # On SWITCH A-Enable RSTP globally(config) spanning-tree mode rstp
## On SWITCH B-Create LAG 1 for connection to Switch
interface lag 1
description "LAG to Switch A"
no shutdown
switchport mode trunk
switchport trunk allowed vlan 1,10,15,25,30-32,40,50-51,60,70,99-100,160,200,999
exit## Use ports 1/0/19 and 1/0/20 as LAG member
interface 1/0/19
description "LAG member to Switch A"
channel-group 1 mode on
exitinterface 1/0/20
description "LAG member to Switch A"
channel-group 1 mode on
exit## On SWITCH C-Create LAG 1 for connection to Switch
interface lag 1
description "LAG to Switch A"
no shutdown
switchport mode trunk
switchport trunk allowed vlan 1,10,15,25,30-32,40,50-51,60,70,99-100,160,200,999
exit! Use ports 1/0/19 and 1/0/20 as LAG members
interface 1/0/19
description "LAG member to Switch A"
channel-group 1 mode on
exitinterface 1/0/20
description "LAG member to Switch A"
channel-group 1 mode on
exitLet me know what you recommendations are as these are currently on live production
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
