Error connecting to BMC
Ryan
troll1602 at gmail.com
Mon Jun 19 19:53:15 UTC 2017
Thanks for the feedback! I do have amttool working, at least getting the
version string back with the 404 error. I was also able to successfully
query/change power states from the MAAS dashboard. However this didn't last
long, as I had MAAS assigning IPs on the same subnet that the AMT static
addresses were set to. It sounds like that's where I messed up.
Like J/Gary are suggesting, I will make sure I have static IPs for AMT and
then I will exclude those IPs from MAAS, ensuring that I have separate IPs
for the BMC and the node.
Thanks for the clarification!
-Ryan
On Mon, Jun 19, 2017 at 11:38 AM, J <dreadpiratejeff at gmail.com> wrote:
> On Thu, Apr 6, 2017 at 4:27 PM, Ryan <troll1602 at gmail.com> wrote:
> > I am having some trouble with power management with nodes via Intel AMT.
> The
> > specific error I am receiving is on the Nodes page for a manually added
> > node, in the Power section:
> >
> > Could not connect to BMC. Check BMC configuration and try again.
> >
> > I'm guessing this error is more a result of my lack of understanding for
> how
> > BMC (specifically Intel AMT) is interacting with DHCP. Are there
> resources
> > online to learn more about this?
>
> So the first thing to check is that you have the right IP and
> password... open a console on the MAAS server and try to get some
> response with amttool (and make sure you actually have amttool
> installed):
>
> bladernr at critical-maas:~$ AMT_PASSWORD=<YOUR AMT PASSWORD> amttool
> 10.0.0.10
> ### AMT info on machine '10.0.0.10' ###
> AMT version: 9.1.0
> 404 Not Found at /usr/bin/amttool line 242.
>
> amttool doesn't work with AMT 9 or newer, but will at least return a
> version string if the login and IP are correct. So if that fails,
> then you need to check the credentials in the node's power settings.
>
> > For example if I set the Power Address for a node (from BIOS menu) to
> > 192.168.10.10 I assuming that I also need to statically assign the same
> IP
> > Address for this node. But does then mean I need to manually add each
> node
> > to MAAS, instead of letting MAAS enlist nodes automatically on that
> subnet?
>
> Incorrect. That entry on the Power settings is for the IP address
> that the BMC already owns. If you have set AMT to get an address via
> DHCP in MEBx, then your BMC is set to some other IP address... I never
> set BMCs to DHCP for this exact reason. it's too easy for confusion,
> and it's also possible that on a renewal down the road, the ME will
> get a DIFFERENT IP address for some reason.
>
> In fact, if you look at the MAAS Dashboard, you'll likely see the AMT
> ME listed there as a device if you have discovery on. But as I said
> before, save yourself the headache, reconfigure AMT with a static IP
> and just use that.
>
>
> >
> > Thanks for the help!
> >
> > MAAS Version 2.1.5+bzr5596-0ubuntu1 (16.04.1)
> >
> > -Ryan M.
> >
> > --
> > Maas-devel mailing list
> > Maas-devel at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/maas-devel
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170619/5a164a3e/attachment-0001.html>
More information about the Maas-devel
mailing list