Hi Stuart,
 
    Is it possible for you to configure the IP on compute nodes as static? you can do it by adding `confignetwork -s` into postscripts. For details, please check https://xcat-docs.readthedocs.io/en/stable/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_ethernet_nic.html?highlight=static%20IP

    And it is recommended not to run `NetworkManager` on compute nodes unless you have special needs, for rhel7, xCAT will disable it by default.
 
Bin Xu
HPC Software Development
Software Defined Infrastructure, IBM Systems
Phone: 86-010-82454067
 
 
----- Original message -----
From: Stuart Barkley <stua...@4gh.net>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Cc:
Subject: Re: [xcat-user] CentOS 7, diskless compute and NetworkManager
Date: Wed, May 30, 2018 10:56 AM
 
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>
> Reply-To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
> To: 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
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

Reply via email to