Hi Yinon, Thanks for raising your issue. I would need a bit more information before I'm able to help you. Please see comments inline:
On Wed, Feb 8, 2017 at 3:51 PM, Yinon <[email protected]> wrote: > Hey, > > I set up a MAAS server. I setup dhcp on untagged interface X. > I pxe boot my 3 nodes, and I see dhcp requests arriving on untagged X on > the MAAS server, un-replied. > Auto discovery doesn't work. > Could you please explain what issues are you really seeing with auto-discovery ? 1. Does the firmware get an IP address from MAAS? 2. Does the machine fail to PXE boot altogether because of 1 or because it cannot reach the TFTP server? 3. Does the machine PXE boot successfully, but is unable to load a kernel/initrd? 4. Does the machine PXE boot successfully, but the ephemeral environment fails somehow ? > When I try to manually add the node, I get: > "(maas-admin) - No rack controllers can access the BMC of node: > dl-360-144" > This means that a MAAS Rack Controller cannot reach the IP address of the BMC of the machine. Can the rack controller route to the BMC of the machine above ? > > all my nodes are HPE DL-360. > > If you think this is a bug, I am happy to report it in launchpad. If not, > any help will be appreciated. > If you could attach some logs that would allow us to determine what the problem is, it would be ideal. If it works best for you, you could file a bug and attach those there. Thanks. > > Thanks, > Yinon > > -- > Maas-devel mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/maas-devel > > -- Andres Rodriguez Engineering Manager, MAAS Canonical USA, Inc.
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
