Is it possible to use Link Aggregation to connect to two unmanaged swtiches, providing switch redundancy? The 2019 Stack Overflow Developer Survey Results Are In Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manara Come Celebrate our 10 Year Anniversary!Link Aggregation between Xserve G4 running Leopard Server and Netgear GSM7224Server-to-Switch Trunking in Procurve switch, what does this mean?Linux bonding: 802.3ad (LACP) vs. balance-alb modeFault Tolerance with 2 HP ProCurve 2824 SwitchesPhysically isolated networks versus link aggregation + VLANsCan I use a server to employ link aggregation between 2 unmanaged switchesHow are we supposed to use linux bonding mode balance-rr?How does one diagnose Linux LACP issues at the kernel level?Does FreeNAS link aggregation work with an unmanaged switch?ESXI NIC Teaming Policy x 2 physical swith x ShaperBGP router
Can a flute soloist sit?
What information about me do stores get via my credit card?
How to determine omitted units in a publication
Why don't hard Brexiteers insist on a hard border to prevent illegal immigration after Brexit?
how can a perfect fourth interval be considered either consonant or dissonant?
Is there a writing software that you can sort scenes like slides in PowerPoint?
How did passengers keep warm on sail ships?
Intergalactic human space ship encounters another ship, character gets shunted off beyond known universe, reality starts collapsing
Can the DM override racial traits?
Drawing vertical/oblique lines in Metrical tree (tikz-qtree, tipa)
Using dividends to reduce short term capital gains?
How do I design a circuit to convert a 100 mV and 50 Hz sine wave to a square wave?
What is the padding with red substance inside of steak packaging?
Is there a way to generate uniformly distributed points on a sphere from a fixed amount of random real numbers per point?
Is every episode of "Where are my Pants?" identical?
How did the crowd guess the pentatonic scale in Bobby McFerrin's presentation?
Why are PDP-7-style microprogrammed instructions out of vogue?
Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
How many cones with angle theta can I pack into the unit sphere?
What other Star Trek series did the main TNG cast show up in?
Homework question about an engine pulling a train
What do I do when my TA workload is more than expected?
Variable with quotation marks "$()"
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
Is it possible to use Link Aggregation to connect to two unmanaged swtiches, providing switch redundancy?
The 2019 Stack Overflow Developer Survey Results Are In
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
Come Celebrate our 10 Year Anniversary!Link Aggregation between Xserve G4 running Leopard Server and Netgear GSM7224Server-to-Switch Trunking in Procurve switch, what does this mean?Linux bonding: 802.3ad (LACP) vs. balance-alb modeFault Tolerance with 2 HP ProCurve 2824 SwitchesPhysically isolated networks versus link aggregation + VLANsCan I use a server to employ link aggregation between 2 unmanaged switchesHow are we supposed to use linux bonding mode balance-rr?How does one diagnose Linux LACP issues at the kernel level?Does FreeNAS link aggregation work with an unmanaged switch?ESXI NIC Teaming Policy x 2 physical swith x ShaperBGP router
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Assuming that I have a firewall that supports Round-Robin or Loadbalance link aggregation (no LACP necessary), would it be possible to connect each of the NICs in the LAGG group to a separate, unmanaged switch?
If I were to then connect a client machine / server with similarly configured bonded NICs, with one cable to each switch, would I then achieve switch redundancy?
All hypothetical at the moment as I try to establish whether switches with LACP would be necessary for this kind of setup.
bonding
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Assuming that I have a firewall that supports Round-Robin or Loadbalance link aggregation (no LACP necessary), would it be possible to connect each of the NICs in the LAGG group to a separate, unmanaged switch?
If I were to then connect a client machine / server with similarly configured bonded NICs, with one cable to each switch, would I then achieve switch redundancy?
All hypothetical at the moment as I try to establish whether switches with LACP would be necessary for this kind of setup.
bonding
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Assuming that I have a firewall that supports Round-Robin or Loadbalance link aggregation (no LACP necessary), would it be possible to connect each of the NICs in the LAGG group to a separate, unmanaged switch?
If I were to then connect a client machine / server with similarly configured bonded NICs, with one cable to each switch, would I then achieve switch redundancy?
All hypothetical at the moment as I try to establish whether switches with LACP would be necessary for this kind of setup.
bonding
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Assuming that I have a firewall that supports Round-Robin or Loadbalance link aggregation (no LACP necessary), would it be possible to connect each of the NICs in the LAGG group to a separate, unmanaged switch?
If I were to then connect a client machine / server with similarly configured bonded NICs, with one cable to each switch, would I then achieve switch redundancy?
All hypothetical at the moment as I try to establish whether switches with LACP would be necessary for this kind of setup.
bonding
bonding
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 10:59
A. JoesburyA. Joesbury
32
32
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
A. Joesbury is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You don't specify what you are using for a firewall, but it is possible with BSD. It's a feature of lagg and does not require using LACP.
From the documenatation:
Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. To configure failover, make sure that the underlying physical interfaces are up, then create the lagg(4) interface. In this example, fxp0 is the master interface, fxp1 is the secondary interface, and the virtual interface is assigned an IP address of 10.0.0.15/24:
# ifconfig fxp0 up
# ifconfig fxp1 up
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24
The virtual interface should look something like this:
# ifconfig lagg0
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0<>
laggport: fxp0 flags=5<MASTER,ACTIVE>
Traffic will be transmitted and received on fxp0. If the link is lost on fxp0, fxp1 will become the active link. If the link is restored on the master interface, it will once again become the active link.
To retain this configuration across reboots, add the following entries to /etc/rc.conf:
ifconfig_fxp0="up"
ifconfig_fxp1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
https://www.freebsd.org/doc/handbook/network-aggregation.html
add a comment |
No (extra characters as serverfault doesn't allow such short responses).
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
1
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
A. Joesbury is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962003%2fis-it-possible-to-use-link-aggregation-to-connect-to-two-unmanaged-swtiches-pro%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You don't specify what you are using for a firewall, but it is possible with BSD. It's a feature of lagg and does not require using LACP.
From the documenatation:
Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. To configure failover, make sure that the underlying physical interfaces are up, then create the lagg(4) interface. In this example, fxp0 is the master interface, fxp1 is the secondary interface, and the virtual interface is assigned an IP address of 10.0.0.15/24:
# ifconfig fxp0 up
# ifconfig fxp1 up
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24
The virtual interface should look something like this:
# ifconfig lagg0
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0<>
laggport: fxp0 flags=5<MASTER,ACTIVE>
Traffic will be transmitted and received on fxp0. If the link is lost on fxp0, fxp1 will become the active link. If the link is restored on the master interface, it will once again become the active link.
To retain this configuration across reboots, add the following entries to /etc/rc.conf:
ifconfig_fxp0="up"
ifconfig_fxp1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
https://www.freebsd.org/doc/handbook/network-aggregation.html
add a comment |
You don't specify what you are using for a firewall, but it is possible with BSD. It's a feature of lagg and does not require using LACP.
From the documenatation:
Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. To configure failover, make sure that the underlying physical interfaces are up, then create the lagg(4) interface. In this example, fxp0 is the master interface, fxp1 is the secondary interface, and the virtual interface is assigned an IP address of 10.0.0.15/24:
# ifconfig fxp0 up
# ifconfig fxp1 up
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24
The virtual interface should look something like this:
# ifconfig lagg0
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0<>
laggport: fxp0 flags=5<MASTER,ACTIVE>
Traffic will be transmitted and received on fxp0. If the link is lost on fxp0, fxp1 will become the active link. If the link is restored on the master interface, it will once again become the active link.
To retain this configuration across reboots, add the following entries to /etc/rc.conf:
ifconfig_fxp0="up"
ifconfig_fxp1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
https://www.freebsd.org/doc/handbook/network-aggregation.html
add a comment |
You don't specify what you are using for a firewall, but it is possible with BSD. It's a feature of lagg and does not require using LACP.
From the documenatation:
Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. To configure failover, make sure that the underlying physical interfaces are up, then create the lagg(4) interface. In this example, fxp0 is the master interface, fxp1 is the secondary interface, and the virtual interface is assigned an IP address of 10.0.0.15/24:
# ifconfig fxp0 up
# ifconfig fxp1 up
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24
The virtual interface should look something like this:
# ifconfig lagg0
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0<>
laggport: fxp0 flags=5<MASTER,ACTIVE>
Traffic will be transmitted and received on fxp0. If the link is lost on fxp0, fxp1 will become the active link. If the link is restored on the master interface, it will once again become the active link.
To retain this configuration across reboots, add the following entries to /etc/rc.conf:
ifconfig_fxp0="up"
ifconfig_fxp1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
https://www.freebsd.org/doc/handbook/network-aggregation.html
You don't specify what you are using for a firewall, but it is possible with BSD. It's a feature of lagg and does not require using LACP.
From the documenatation:
Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. To configure failover, make sure that the underlying physical interfaces are up, then create the lagg(4) interface. In this example, fxp0 is the master interface, fxp1 is the secondary interface, and the virtual interface is assigned an IP address of 10.0.0.15/24:
# ifconfig fxp0 up
# ifconfig fxp1 up
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24
The virtual interface should look something like this:
# ifconfig lagg0
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0<>
laggport: fxp0 flags=5<MASTER,ACTIVE>
Traffic will be transmitted and received on fxp0. If the link is lost on fxp0, fxp1 will become the active link. If the link is restored on the master interface, it will once again become the active link.
To retain this configuration across reboots, add the following entries to /etc/rc.conf:
ifconfig_fxp0="up"
ifconfig_fxp1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
https://www.freebsd.org/doc/handbook/network-aggregation.html
answered Apr 8 at 13:09
BertBert
80057
80057
add a comment |
add a comment |
No (extra characters as serverfault doesn't allow such short responses).
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
1
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
add a comment |
No (extra characters as serverfault doesn't allow such short responses).
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
1
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
add a comment |
No (extra characters as serverfault doesn't allow such short responses).
No (extra characters as serverfault doesn't allow such short responses).
answered Apr 8 at 11:09
Chopper3Chopper3
94.7k999227
94.7k999227
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
1
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
add a comment |
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
1
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
I'd really appreciate some details as to why this setup wouldn't work. Thanks
– A. Joesbury
Apr 8 at 11:24
1
1
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
Only one switch should be advertising any given MAC address at any given time, this is possible with intelligent/managed switches that are aware of each other's CAM tables (such as Cisco's VSS system) but when you connect a LAG to two switches that don't know anything about each other then almost all of the time the MAC is 'flapping' between both switches and you get packet drops all the time.
– Chopper3
Apr 8 at 11:31
add a comment |
A. Joesbury is a new contributor. Be nice, and check out our Code of Conduct.
A. Joesbury is a new contributor. Be nice, and check out our Code of Conduct.
A. Joesbury is a new contributor. Be nice, and check out our Code of Conduct.
A. Joesbury is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962003%2fis-it-possible-to-use-link-aggregation-to-connect-to-two-unmanaged-swtiches-pro%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown