Problem booting node with PXE Ubuntu MAAS
I'm having problem with adding nodes in Ubuntu MAAS, it boots when I'm adding it in web interface but when the node boots it doesn't boot any PXE files or find the master computer.
PXE-E76: Bad or missing multicast discovery address
PXE-M0F: Exiting HP PXE ROOM
maas
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm having problem with adding nodes in Ubuntu MAAS, it boots when I'm adding it in web interface but when the node boots it doesn't boot any PXE files or find the master computer.
PXE-E76: Bad or missing multicast discovery address
PXE-M0F: Exiting HP PXE ROOM
maas
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm having problem with adding nodes in Ubuntu MAAS, it boots when I'm adding it in web interface but when the node boots it doesn't boot any PXE files or find the master computer.
PXE-E76: Bad or missing multicast discovery address
PXE-M0F: Exiting HP PXE ROOM
maas
I'm having problem with adding nodes in Ubuntu MAAS, it boots when I'm adding it in web interface but when the node boots it doesn't boot any PXE files or find the master computer.
PXE-E76: Bad or missing multicast discovery address
PXE-M0F: Exiting HP PXE ROOM
maas
maas
edited Oct 5 '12 at 15:57
Peachy
5,06672843
5,06672843
asked Sep 18 '12 at 8:55
Anders UrdalAnders Urdal
613
613
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
So next-server in your dhcpd config is pointing to the IP address of the maas server? If it's not then PXE doesn't know where to retrieve pxelinux.0 (tftp server), also I don't see that pxe file name in your output either. Go back to the docs and verify that your DHCP server config is setup correctly according to your environment e.g. maas owns the network or using an existing dhcp server. It's also helpful for only one interface on your maas clients to acknowledge PXE boot.
If you have that all sorted see: http://www.networkingblog.in/ios-dhcp-pxe-and-ip-helper-address-5363
"Kumar April 13, 2010 at 6:53 am
I think your PXE clients are using MTFTP which uses Multicast. Again this traffic wont be forward using helper-address as its not a broadcast. ITs a multicast. YOu will need to enable multicast forwarding on your router to forward this multicast TFTP traffic to the PXE server which holds the bootfile. It works in the adjacent vlan, as the clients are on the same LAN as the PXE server. Can you put a sniffer such as ethereal and filter multicast packets and see what Multicast packet on port 69 is used (TFTP). THen you can enable PIM routing to forward multicast traffic from this vlan to the PXE server vlan.
Here is a guide to multicast routing.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca794.html#wp1000948
Here is a link to ethereal – download."
Has PXE boot ever worked on your network before?
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%2f190094%2fproblem-booting-node-with-pxe-ubuntu-maas%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
So next-server in your dhcpd config is pointing to the IP address of the maas server? If it's not then PXE doesn't know where to retrieve pxelinux.0 (tftp server), also I don't see that pxe file name in your output either. Go back to the docs and verify that your DHCP server config is setup correctly according to your environment e.g. maas owns the network or using an existing dhcp server. It's also helpful for only one interface on your maas clients to acknowledge PXE boot.
If you have that all sorted see: http://www.networkingblog.in/ios-dhcp-pxe-and-ip-helper-address-5363
"Kumar April 13, 2010 at 6:53 am
I think your PXE clients are using MTFTP which uses Multicast. Again this traffic wont be forward using helper-address as its not a broadcast. ITs a multicast. YOu will need to enable multicast forwarding on your router to forward this multicast TFTP traffic to the PXE server which holds the bootfile. It works in the adjacent vlan, as the clients are on the same LAN as the PXE server. Can you put a sniffer such as ethereal and filter multicast packets and see what Multicast packet on port 69 is used (TFTP). THen you can enable PIM routing to forward multicast traffic from this vlan to the PXE server vlan.
Here is a guide to multicast routing.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca794.html#wp1000948
Here is a link to ethereal – download."
Has PXE boot ever worked on your network before?
add a comment |
So next-server in your dhcpd config is pointing to the IP address of the maas server? If it's not then PXE doesn't know where to retrieve pxelinux.0 (tftp server), also I don't see that pxe file name in your output either. Go back to the docs and verify that your DHCP server config is setup correctly according to your environment e.g. maas owns the network or using an existing dhcp server. It's also helpful for only one interface on your maas clients to acknowledge PXE boot.
If you have that all sorted see: http://www.networkingblog.in/ios-dhcp-pxe-and-ip-helper-address-5363
"Kumar April 13, 2010 at 6:53 am
I think your PXE clients are using MTFTP which uses Multicast. Again this traffic wont be forward using helper-address as its not a broadcast. ITs a multicast. YOu will need to enable multicast forwarding on your router to forward this multicast TFTP traffic to the PXE server which holds the bootfile. It works in the adjacent vlan, as the clients are on the same LAN as the PXE server. Can you put a sniffer such as ethereal and filter multicast packets and see what Multicast packet on port 69 is used (TFTP). THen you can enable PIM routing to forward multicast traffic from this vlan to the PXE server vlan.
Here is a guide to multicast routing.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca794.html#wp1000948
Here is a link to ethereal – download."
Has PXE boot ever worked on your network before?
add a comment |
So next-server in your dhcpd config is pointing to the IP address of the maas server? If it's not then PXE doesn't know where to retrieve pxelinux.0 (tftp server), also I don't see that pxe file name in your output either. Go back to the docs and verify that your DHCP server config is setup correctly according to your environment e.g. maas owns the network or using an existing dhcp server. It's also helpful for only one interface on your maas clients to acknowledge PXE boot.
If you have that all sorted see: http://www.networkingblog.in/ios-dhcp-pxe-and-ip-helper-address-5363
"Kumar April 13, 2010 at 6:53 am
I think your PXE clients are using MTFTP which uses Multicast. Again this traffic wont be forward using helper-address as its not a broadcast. ITs a multicast. YOu will need to enable multicast forwarding on your router to forward this multicast TFTP traffic to the PXE server which holds the bootfile. It works in the adjacent vlan, as the clients are on the same LAN as the PXE server. Can you put a sniffer such as ethereal and filter multicast packets and see what Multicast packet on port 69 is used (TFTP). THen you can enable PIM routing to forward multicast traffic from this vlan to the PXE server vlan.
Here is a guide to multicast routing.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca794.html#wp1000948
Here is a link to ethereal – download."
Has PXE boot ever worked on your network before?
So next-server in your dhcpd config is pointing to the IP address of the maas server? If it's not then PXE doesn't know where to retrieve pxelinux.0 (tftp server), also I don't see that pxe file name in your output either. Go back to the docs and verify that your DHCP server config is setup correctly according to your environment e.g. maas owns the network or using an existing dhcp server. It's also helpful for only one interface on your maas clients to acknowledge PXE boot.
If you have that all sorted see: http://www.networkingblog.in/ios-dhcp-pxe-and-ip-helper-address-5363
"Kumar April 13, 2010 at 6:53 am
I think your PXE clients are using MTFTP which uses Multicast. Again this traffic wont be forward using helper-address as its not a broadcast. ITs a multicast. YOu will need to enable multicast forwarding on your router to forward this multicast TFTP traffic to the PXE server which holds the bootfile. It works in the adjacent vlan, as the clients are on the same LAN as the PXE server. Can you put a sniffer such as ethereal and filter multicast packets and see what Multicast packet on port 69 is used (TFTP). THen you can enable PIM routing to forward multicast traffic from this vlan to the PXE server vlan.
Here is a guide to multicast routing.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca794.html#wp1000948
Here is a link to ethereal – download."
Has PXE boot ever worked on your network before?
answered Oct 11 '12 at 13:37
ppetrakippetraki
4,8601750
4,8601750
add a comment |
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%2f190094%2fproblem-booting-node-with-pxe-ubuntu-maas%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