Note that in such a case, would have to do firmware updates for UEFI and IMM
remotely (not the worst thing in the world). Another alternative is to disable
it in firmware:
# nodeconfig s1 IMM.LanOverUsb=disable
Or
# pasu s1 set IMM.LanOverUsb Disabled
This is a point of interest as there is a push to migrate more in-band
instrumentation toward using that USB nic, to the point of some folks asking to
remove IPMI KCS (which I oppose personally, never been a fan of IP as an
‘within-the-box’ protocol, precisely because software has understandably
assumed ‘network’ meant talking to other systems not internal point to point).
At the very least I’m pushing to no longer DHCPOFFER anything on that
interface, and rework the software to use fe80:: addressing instead to avoid
any network that OpenMPI or other similarly optimistic software getting
confused by non-viable networks.
As a point of historical interest, originally it did not DHCPOFFER, but some OS
boot would block waiting for DHCP to complete, so the DHCPOFFER was done to
speed up boot process of those platforms. I don’t think any OS would be foiled
by a link but no DHCP offer on a stray network anymore.
None of this is likely to happen in currently or past shipped product, but
would be effective as of the release of future product.
From: Kevin Keane <kke...@sandiego.edu>
Sent: Wednesday, May 30, 2018 12:20 PM
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Subject: [External] Re: [xcat-user] CentOS 7, diskless compute and
NetworkManager
I had a similar problem with the USB-based IPMI network interfaces. I
blacklisted the driver. In the image for your node, add the following file:
/etc/modprobe.d/usbeth_blacklist.conf
With the content (verify that cdc_ether is the correct driver first!)
blacklist cdc_ether
You can probably also edit /etc/sysconfig/network-scripts/ifcfg-usb0 and set
ONBOOT=no
_______________________________________________________________________
Kevin Keane | Systems Architect | University of San Diego ITS |
kke...@sandiego.edu<mailto:kke...@sandiego.edu>
Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 |
619.260.6859<tel:%28619%29%20260-2298>
REMEMBER! No one from IT at USD will ever ask to confirm or supply your
password.
These messages are an attempt to steal your username and password. Please do
not reply to, click the links within, or open the attachments of these
messages. Delete them!
On Tue, May 29, 2018 at 7:43 PM, Stuart Barkley
<stua...@4gh.net<mailto:stua...@4gh.net>> wrote:
I haven't seen a response to the question below.
Should I expect to be running NetworkManager on diskless compute nodes
with CentOS 7 and xCAT 2.13.X?
When deploying the updated compute image on certain nodes, I'm now
finding NetworkManager bringing up unwanted interfaces using dhcp.
Specifically, on our IBM compute nodes DHCP is bringing up the usb
based network interface to the IPMI device confusing OpenMPI.
Thanks for any insights,
Stuart
[Also, I've been having problems sending email to this list for the
last few months. Perhaps it is time to migrate the mailing list off
of sourceforge.]
On Mon, 5 Mar 2018 at 21:20 -0000, Stuart Barkley wrote:
> Date: Mon, 5 Mar 2018 21:20:25
> From: Stuart Barkley <stua...@4gh.net<mailto:stua...@4gh.net>>
> Reply-To: xCAT Users Mailing list
> <xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>>
> To: xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>
> Subject: [xcat-user] CentOS 7, diskless compute and NetworkManager
>
> What is the current recommended configuration regarding NetworkManager
> for diskless compute nodes (CentOS 7.3/7.4)?
>
> We are upgrading xCAT with a large jump (from 2.8 to 2.13.8) and
> running into issues with our compute images losing IP address after 12
> hours (dhclient is not running). The Release Notes for 2.13 show
> Issue 1972 as being resolved, but this sounds like the problem we are
> seeing.
>
> <https://github.com/xcat2/xcat-core/issues/1972> has a long set of
> comments and some of the referenced patches seem to be applied.
> <https://github.com/xcat2/xcat-core/issues/1972#issuecomment-254120700>
> references a fix <https://github.com/xcat2/xcat-core/pull/1977/files>
> which adds NetworkManager to the compute image. This change seems to
> address our problem, but does not seem to have made it into mainline
> xCAT.
>
> In general, I would prefer to not have NetworkManager running, but
> that is mostly a historical bias. NetworkManager does bring in a few
> unneeded modules (ppp and wireless support in particular), but I can
> live with it if necessary.
>
> We are not explicitly running hardeths, configeth or anything similar.
>
> Is NetworkManager required? Or should I remove it and search for some
> other cause of the problem?
>
> Thanks for any suggestions,
> Stuart Barkley
> --
> I've never been lost; I was once bewildered for three days, but never lost!
> -- Daniel Boone
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
