Netplan Different Machine
I am currently trying to install Ubuntu 18.10 on a HP X310 headless server with no VGA port. Due to this I am unable to install directly on the machine. I have a system with similar specs and same networking chip that I am able to install on, then swap the hard drive over. This appears to work, but I cannot get the network port working. I know this because I am able to blind type 'shutdown now' and it will work.
Is there a way in netplan to force the system to update the network card on the next boot, or is there a way to blind type a command that would make netplan configured the new network port?
server 18.10 netplan
asked Dec 13 '18 at 20:21
DanielDaniel
82
add a comment |
I am currently trying to install Ubuntu 18.10 on a HP X310 headless server with no VGA port. Due to this I am unable to install directly on the machine. I have a system with similar specs and same networking chip that I am able to install on, then swap the hard drive over. This appears to work, but I cannot get the network port working. I know this because I am able to blind type 'shutdown now' and it will work.
Is there a way in netplan to force the system to update the network card on the next boot, or is there a way to blind type a command that would make netplan configured the new network port?
server 18.10 netplan
asked Dec 13 '18 at 20:21
DanielDaniel
82
add a comment |
I am currently trying to install Ubuntu 18.10 on a HP X310 headless server with no VGA port. Due to this I am unable to install directly on the machine. I have a system with similar specs and same networking chip that I am able to install on, then swap the hard drive over. This appears to work, but I cannot get the network port working. I know this because I am able to blind type 'shutdown now' and it will work.
Is there a way in netplan to force the system to update the network card on the next boot, or is there a way to blind type a command that would make netplan configured the new network port?
server 18.10 netplan
asked Dec 13 '18 at 20:21
DanielDaniel
82
I am currently trying to install Ubuntu 18.10 on a HP X310 headless server with no VGA port. Due to this I am unable to install directly on the machine. I have a system with similar specs and same networking chip that I am able to install on, then swap the hard drive over. This appears to work, but I cannot get the network port working. I know this because I am able to blind type 'shutdown now' and it will work.
Is there a way in netplan to force the system to update the network card on the next boot, or is there a way to blind type a command that would make netplan configured the new network port?
server 18.10 netplan
server 18.10 netplan
asked Dec 13 '18 at 20:21
DanielDaniel
82
asked Dec 13 '18 at 20:21
DanielDaniel
82
asked Dec 13 '18 at 20:21
DanielDaniel
82
asked Dec 13 '18 at 20:21
DanielDaniel
82
asked Dec 13 '18 at 20:21
DanielDaniel
82
82
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Try this...
Install the hard disk into your working server system.
Edit /etc/default/grub. Find the line, near the top, that includes "quiet splash" and add "net.ifnames=0". This will make the network devices have standard, old school, device names. Your ethernet device will almost certainly become eth0 instead of some strange variable name like ens01p01. Then do sudo update-grub. Then reboot.
Edit /etc/netplan/*.yaml and change the ethernets: device definition from ens01p01 to eth0. Then sudo netplan --debug generate and sudo netplan apply.
Reboot the computer and use ifconfig to confirm that the ethernet device is eth0. If not, you'll need to modify the .yaml file indicated earlier.
Move the hard disk to the primary server, and it should all work.
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
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%2f1100718%2fnetplan-different-machine%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
Try this...
Install the hard disk into your working server system.
Edit /etc/default/grub. Find the line, near the top, that includes "quiet splash" and add "net.ifnames=0". This will make the network devices have standard, old school, device names. Your ethernet device will almost certainly become eth0 instead of some strange variable name like ens01p01. Then do sudo update-grub. Then reboot.
Edit /etc/netplan/*.yaml and change the ethernets: device definition from ens01p01 to eth0. Then sudo netplan --debug generate and sudo netplan apply.
Reboot the computer and use ifconfig to confirm that the ethernet device is eth0. If not, you'll need to modify the .yaml file indicated earlier.
Move the hard disk to the primary server, and it should all work.
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
add a comment |
Try this...
Install the hard disk into your working server system.
Edit /etc/default/grub. Find the line, near the top, that includes "quiet splash" and add "net.ifnames=0". This will make the network devices have standard, old school, device names. Your ethernet device will almost certainly become eth0 instead of some strange variable name like ens01p01. Then do sudo update-grub. Then reboot.
Edit /etc/netplan/*.yaml and change the ethernets: device definition from ens01p01 to eth0. Then sudo netplan --debug generate and sudo netplan apply.
Reboot the computer and use ifconfig to confirm that the ethernet device is eth0. If not, you'll need to modify the .yaml file indicated earlier.
Move the hard disk to the primary server, and it should all work.
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
add a comment |
Try this...
Install the hard disk into your working server system.
Edit /etc/default/grub. Find the line, near the top, that includes "quiet splash" and add "net.ifnames=0". This will make the network devices have standard, old school, device names. Your ethernet device will almost certainly become eth0 instead of some strange variable name like ens01p01. Then do sudo update-grub. Then reboot.
Edit /etc/netplan/*.yaml and change the ethernets: device definition from ens01p01 to eth0. Then sudo netplan --debug generate and sudo netplan apply.
Reboot the computer and use ifconfig to confirm that the ethernet device is eth0. If not, you'll need to modify the .yaml file indicated earlier.
Move the hard disk to the primary server, and it should all work.
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
Try this...
Install the hard disk into your working server system.
Edit /etc/default/grub. Find the line, near the top, that includes "quiet splash" and add "net.ifnames=0". This will make the network devices have standard, old school, device names. Your ethernet device will almost certainly become eth0 instead of some strange variable name like ens01p01. Then do sudo update-grub. Then reboot.
Edit /etc/netplan/*.yaml and change the ethernets: device definition from ens01p01 to eth0. Then sudo netplan --debug generate and sudo netplan apply.
Reboot the computer and use ifconfig to confirm that the ethernet device is eth0. If not, you'll need to modify the .yaml file indicated earlier.
Move the hard disk to the primary server, and it should all work.
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
edited 9 mins ago
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
answered Dec 13 '18 at 21:02
heynnemaheynnema
18.7k22155
18.7k22155
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
add a comment |
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
That worked great! After the first reboot the network port didn't show at all in ifconfig, but after edititing the *.yaml file as you suggested and rebooting it worked great. Thanks!
– Daniel
Dec 14 '18 at 2:06
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI... from another question that we worked on together... get ready to "pick yourself up off of the floor"... this method does work! We had never received closure on the other question.
– heynnema
Dec 15 '18 at 14:40
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@chili555 FYI #2... for reference, it was askubuntu.com/questions/1089580/…
– heynnema
Dec 15 '18 at 14:49
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
@heynnema I am always happy to be enlightened. I hope to learn more every day. Thanks for the heads up. A very clever solution!
– chili555
Dec 18 '18 at 2:38
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%2f1100718%2fnetplan-different-machine%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
