Ubuntu: ethX Interface not bonded after unplugging and plugging its cable back
I am trying to set up fail-back configuration in bonding but I am unable to get around the interface configuration. My interface is as follow:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
up /sbin/ifenslave bond0 eth1 eth3
down /sbin/ifenslave -d bond0 eth1 eth3
My /etc/modprobe.d/bonding.conf file is:
alias bond0 bonding
options bonding mode=3
I test it by running ping from other system. My bond status is as follows:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
When I remove eth1 cable the fail-over works and eth3 carries out the data (The ping still continues).
If I connect back eth1 and remove eth3 the ping stops and the bonding status doesn't contain any of the interface. The bond status is:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
I tried with all the modes in the bonding ( 0 to 6 ). But none of the configuration provides the fail-back support. Where am I going wrong?
network-bonding failover high-availability
add a comment |
I am trying to set up fail-back configuration in bonding but I am unable to get around the interface configuration. My interface is as follow:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
up /sbin/ifenslave bond0 eth1 eth3
down /sbin/ifenslave -d bond0 eth1 eth3
My /etc/modprobe.d/bonding.conf file is:
alias bond0 bonding
options bonding mode=3
I test it by running ping from other system. My bond status is as follows:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
When I remove eth1 cable the fail-over works and eth3 carries out the data (The ping still continues).
If I connect back eth1 and remove eth3 the ping stops and the bonding status doesn't contain any of the interface. The bond status is:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
I tried with all the modes in the bonding ( 0 to 6 ). But none of the configuration provides the fail-back support. Where am I going wrong?
network-bonding failover high-availability
add a comment |
I am trying to set up fail-back configuration in bonding but I am unable to get around the interface configuration. My interface is as follow:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
up /sbin/ifenslave bond0 eth1 eth3
down /sbin/ifenslave -d bond0 eth1 eth3
My /etc/modprobe.d/bonding.conf file is:
alias bond0 bonding
options bonding mode=3
I test it by running ping from other system. My bond status is as follows:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
When I remove eth1 cable the fail-over works and eth3 carries out the data (The ping still continues).
If I connect back eth1 and remove eth3 the ping stops and the bonding status doesn't contain any of the interface. The bond status is:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
I tried with all the modes in the bonding ( 0 to 6 ). But none of the configuration provides the fail-back support. Where am I going wrong?
network-bonding failover high-availability
I am trying to set up fail-back configuration in bonding but I am unable to get around the interface configuration. My interface is as follow:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
up /sbin/ifenslave bond0 eth1 eth3
down /sbin/ifenslave -d bond0 eth1 eth3
My /etc/modprobe.d/bonding.conf file is:
alias bond0 bonding
options bonding mode=3
I test it by running ping from other system. My bond status is as follows:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 44:a8:42:03:68:2c
Slave queue ID: 0
When I remove eth1 cable the fail-over works and eth3 carries out the data (The ping still continues).
If I connect back eth1 and remove eth3 the ping stops and the bonding status doesn't contain any of the interface. The bond status is:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
I tried with all the modes in the bonding ( 0 to 6 ). But none of the configuration provides the fail-back support. Where am I going wrong?
network-bonding failover high-availability
network-bonding failover high-availability
asked Nov 18 '15 at 5:43
Paul JustinPaul Justin
192
192
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
EDIT 2019-01-10: These instructions are for Ubuntu 16.04 and older. I will try to update with instructions for 18.04.
In this answer, we are using active-backup
bonding with a bond-primary
interface set that allows for fail-over to go back to the primary when it is available. More information can be found: https://wiki.linuxfoundation.org/networking/bonding
Bonding in Ubuntu is a different setup then as in other distros of Linux like RedHat. I have done a few bonding configurations in Ubuntu and I will lay it out below as best as possible.
As it looks, you already have ifenslave
installed, but if not, install ifenslave
:
sudo apt-get install ifenslave
Next, take a look at /etc/modules
and make sure it has the following lines:
loop
lp
rtc
bonding
In the /etc/network/interfaces
file, set your loopback
, eth1
, and eth3
interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet manual
bond-master bond0
bond-primary eth1
auto eth3
iface eth3 inet manual
bond-master bond0
Now set your bond0
interface with active-backup
for fail-over if one of the NIC connections fail:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
bond-mode active-backup
bond-miimon 100
bond-slaves none
Save the changes to /etc/network/interfaces
file and restart your networking service:
sudo /etc/init.d/networking restart
Now you can check your bonding setup. Make sure that your bond0
, eth1
and eth3
are correct:
sudo ethtool bond0
sudo ethtool eth1
sudo ethtool eth3
Check to see if fail-over now works by removing eth1
from bond0
:
sudo ifenslave -d bond0 eth1
Check to see if you can still ping the gateway:
ping -c2 192.168.1.1
Add eth1
back to bond0
:
sudo ifenslave bond0 eth1
Hope this helps!
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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
});
}
});
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%2faskubuntu.com%2fquestions%2f699422%2fubuntu-ethx-interface-not-bonded-after-unplugging-and-plugging-its-cable-back%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
EDIT 2019-01-10: These instructions are for Ubuntu 16.04 and older. I will try to update with instructions for 18.04.
In this answer, we are using active-backup
bonding with a bond-primary
interface set that allows for fail-over to go back to the primary when it is available. More information can be found: https://wiki.linuxfoundation.org/networking/bonding
Bonding in Ubuntu is a different setup then as in other distros of Linux like RedHat. I have done a few bonding configurations in Ubuntu and I will lay it out below as best as possible.
As it looks, you already have ifenslave
installed, but if not, install ifenslave
:
sudo apt-get install ifenslave
Next, take a look at /etc/modules
and make sure it has the following lines:
loop
lp
rtc
bonding
In the /etc/network/interfaces
file, set your loopback
, eth1
, and eth3
interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet manual
bond-master bond0
bond-primary eth1
auto eth3
iface eth3 inet manual
bond-master bond0
Now set your bond0
interface with active-backup
for fail-over if one of the NIC connections fail:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
bond-mode active-backup
bond-miimon 100
bond-slaves none
Save the changes to /etc/network/interfaces
file and restart your networking service:
sudo /etc/init.d/networking restart
Now you can check your bonding setup. Make sure that your bond0
, eth1
and eth3
are correct:
sudo ethtool bond0
sudo ethtool eth1
sudo ethtool eth3
Check to see if fail-over now works by removing eth1
from bond0
:
sudo ifenslave -d bond0 eth1
Check to see if you can still ping the gateway:
ping -c2 192.168.1.1
Add eth1
back to bond0
:
sudo ifenslave bond0 eth1
Hope this helps!
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
add a comment |
EDIT 2019-01-10: These instructions are for Ubuntu 16.04 and older. I will try to update with instructions for 18.04.
In this answer, we are using active-backup
bonding with a bond-primary
interface set that allows for fail-over to go back to the primary when it is available. More information can be found: https://wiki.linuxfoundation.org/networking/bonding
Bonding in Ubuntu is a different setup then as in other distros of Linux like RedHat. I have done a few bonding configurations in Ubuntu and I will lay it out below as best as possible.
As it looks, you already have ifenslave
installed, but if not, install ifenslave
:
sudo apt-get install ifenslave
Next, take a look at /etc/modules
and make sure it has the following lines:
loop
lp
rtc
bonding
In the /etc/network/interfaces
file, set your loopback
, eth1
, and eth3
interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet manual
bond-master bond0
bond-primary eth1
auto eth3
iface eth3 inet manual
bond-master bond0
Now set your bond0
interface with active-backup
for fail-over if one of the NIC connections fail:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
bond-mode active-backup
bond-miimon 100
bond-slaves none
Save the changes to /etc/network/interfaces
file and restart your networking service:
sudo /etc/init.d/networking restart
Now you can check your bonding setup. Make sure that your bond0
, eth1
and eth3
are correct:
sudo ethtool bond0
sudo ethtool eth1
sudo ethtool eth3
Check to see if fail-over now works by removing eth1
from bond0
:
sudo ifenslave -d bond0 eth1
Check to see if you can still ping the gateway:
ping -c2 192.168.1.1
Add eth1
back to bond0
:
sudo ifenslave bond0 eth1
Hope this helps!
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
add a comment |
EDIT 2019-01-10: These instructions are for Ubuntu 16.04 and older. I will try to update with instructions for 18.04.
In this answer, we are using active-backup
bonding with a bond-primary
interface set that allows for fail-over to go back to the primary when it is available. More information can be found: https://wiki.linuxfoundation.org/networking/bonding
Bonding in Ubuntu is a different setup then as in other distros of Linux like RedHat. I have done a few bonding configurations in Ubuntu and I will lay it out below as best as possible.
As it looks, you already have ifenslave
installed, but if not, install ifenslave
:
sudo apt-get install ifenslave
Next, take a look at /etc/modules
and make sure it has the following lines:
loop
lp
rtc
bonding
In the /etc/network/interfaces
file, set your loopback
, eth1
, and eth3
interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet manual
bond-master bond0
bond-primary eth1
auto eth3
iface eth3 inet manual
bond-master bond0
Now set your bond0
interface with active-backup
for fail-over if one of the NIC connections fail:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
bond-mode active-backup
bond-miimon 100
bond-slaves none
Save the changes to /etc/network/interfaces
file and restart your networking service:
sudo /etc/init.d/networking restart
Now you can check your bonding setup. Make sure that your bond0
, eth1
and eth3
are correct:
sudo ethtool bond0
sudo ethtool eth1
sudo ethtool eth3
Check to see if fail-over now works by removing eth1
from bond0
:
sudo ifenslave -d bond0 eth1
Check to see if you can still ping the gateway:
ping -c2 192.168.1.1
Add eth1
back to bond0
:
sudo ifenslave bond0 eth1
Hope this helps!
EDIT 2019-01-10: These instructions are for Ubuntu 16.04 and older. I will try to update with instructions for 18.04.
In this answer, we are using active-backup
bonding with a bond-primary
interface set that allows for fail-over to go back to the primary when it is available. More information can be found: https://wiki.linuxfoundation.org/networking/bonding
Bonding in Ubuntu is a different setup then as in other distros of Linux like RedHat. I have done a few bonding configurations in Ubuntu and I will lay it out below as best as possible.
As it looks, you already have ifenslave
installed, but if not, install ifenslave
:
sudo apt-get install ifenslave
Next, take a look at /etc/modules
and make sure it has the following lines:
loop
lp
rtc
bonding
In the /etc/network/interfaces
file, set your loopback
, eth1
, and eth3
interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet manual
bond-master bond0
bond-primary eth1
auto eth3
iface eth3 inet manual
bond-master bond0
Now set your bond0
interface with active-backup
for fail-over if one of the NIC connections fail:
auto bond0
iface bond0 inet static
address 192.168.1.39
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
bond-mode active-backup
bond-miimon 100
bond-slaves none
Save the changes to /etc/network/interfaces
file and restart your networking service:
sudo /etc/init.d/networking restart
Now you can check your bonding setup. Make sure that your bond0
, eth1
and eth3
are correct:
sudo ethtool bond0
sudo ethtool eth1
sudo ethtool eth3
Check to see if fail-over now works by removing eth1
from bond0
:
sudo ifenslave -d bond0 eth1
Check to see if you can still ping the gateway:
ping -c2 192.168.1.1
Add eth1
back to bond0
:
sudo ifenslave bond0 eth1
Hope this helps!
edited Jan 10 at 14:48
answered Nov 18 '15 at 16:35
TerranceTerrance
19.1k34797
19.1k34797
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
add a comment |
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
This answers the question indirectly. I wanted automated fail-back after connecting physical cable. I managed to attain that by adding a script in ifup/ifdown folder.
– Paul Justin
Aug 10 '17 at 5:14
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin Did you even try this suggested answer or did you go another route for your own?
– Terrance
Aug 10 '17 at 5:18
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@PaulJustin If you found a solution not already posted that fixed your problem, I recommend posting it as an answer yourself. Your answer could describe how you added the script and give the contents of the script (possibly with modifications or redaction, if you feel that is necessary), and any other information that would help someone else use your solution. Then future readers who arrive here will be able to benefit both from this answer and your answer.
– Eliah Kagan
Aug 10 '17 at 15:37
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Terrance we have followed your steps for active backup in ubuntu 18.04 server, Though the configurations are set, but there is no internet connection.
– Purushothaman
Jan 10 at 8:27
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
@Purushothaman 18.04 has a different way of configuring active backup. I will have to write another answer or add on a new section to this one about doing it. Sorry that this one didn't work for now.
– Terrance
Jan 10 at 14:42
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f699422%2fubuntu-ethx-interface-not-bonded-after-unplugging-and-plugging-its-cable-back%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