bmcsetup does a lot of stuff that IBM systems don't need to have done, it
is intended to support as many IPMI implementations as is reasonable.  We
used to downgrade OEM to Administrator privilege in a few cases that caused
some problems on other systems, but now we even leave OEM privilege level
alone when encountered.  It used to assume channel 1 was 'the' LAN channel,
now it seeks out one in the event that isn't the case.



From:   Ryan Enge <[email protected]>
To:     xCAT Users Mailing list <[email protected]>,
Date:   03/14/2012 11:58 AM
Subject:        Re: [xcat-user] xCAT bmcsetup troubles



Hi Russell,

I thought I would reply off list for now, we have just received some Dell
C6100 series nodes and I was under the impression that xCat could not
program the BMC for these nodes. Did you have do do any manual
configuration in the BMC or make any changes to the xCat code to get this
working?

On 03/14/2012 07:43 AM, Russell Jones wrote:
      Hi all,

      Putting together a rack of some Dell c6100 series nodes, and am
      running into some strange bmcsetup errors.

      Everything appears to be configured properly on the xcat management
      node, both the compute and the BMC networks all ping without an
      issue. When I tell a node to do a bmcsetup, it displays the following
      error on the screen:

      Unable to prove root on your IP approves of this request



      It then waits for a random period of time, tries again and always
      succeeds the second time with no errors being shown.

      The management node does not have access to the internet, and as a
      result it is also dumping these bind warnings out
      to /var/log/messages. These only appear when the compute node is
      requesting config parameters from the MN:

      Mar 13 10:46:24 linux7mgt named[6915]: too many timeouts resolving
      '0/A' (in '.'?): disabling EDNS
      Mar 13 10:46:24 linux7mgt named[6915]: too many timeouts resolving
      './NS' (in '.'?): disabling EDNS
      Mar 13 10:46:24 linux7mgt named[6915]: too many timeouts resolving
      'C.ROOT-SERVERS.NET/AAAA' (in '.'?): disabling EDNS
      Mar 13 10:46:24 linux7mgt named[6915]: too many timeouts resolving
      'C.ROOT-SERVERS.NET/AAAA' (in '.'?): disabling EDNS
      Mar 13 10:46:24 linux7mgt named[6915]: too many timeouts resolving
      'C.ROOT-SERVERS.NET/AAAA' (in '.'?): disabling EDNS
      Mar 13 10:46:24 linux7mgt named[6915]: too many timeouts resolving
      'L.ROOT-SERVERS.NET/AAAA' (in '.'?): disabling EDNS



      Could these issues be a side effect of bind not having access to the
      internet to do root DNS lookups? It seems unlikely, but given that it
      seems to always succeed a second time, and after succeeding
      everything works perfectly, I'm at a loss.


      Thanks for any help!




--
Ryan Enge
Senior Systems Administrator
University Systems
University of Victoria
Room: CLE D063
Phone: 250.472.5447
Cell: 250.516.4975
------------------------------------------------------------------------------

Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

<<inline: graycol.gif>>

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to