Is this when we leave it blank? In that case, it indicates 'whatever mac
address could pxe boot' rather than trying to name names.
I've also considered the possibility of having a name field to force the
nic name to be something that would be recognized (whether its 'eth0' or
'bob3'), using the aforementioned 'just whatever booted' as a starter and
slapping a reasonable name at the end. Considering right now one of my
nodes installed over 'enp12s0f1' I certainly am happy that our
autodetection stuff worked, but that's an annoying name ongoing and we
probably should provide a nice mechanism to make the name mean something
nice (since 'eth0' and friends are admittedly sometimes unpredictable by
default, something in the middle could be nice that would be both
consistent boot to boot, device to device but also from node to node (which
CNDN breaks pretty thoroughly).
From: deheller <[email protected]>
To: [email protected]
Date: 07/10/2014 11:01 AM
Subject: Re: [xcat-user] ksdevice problem
FWIW: I have observed that distros are relying more on Consistent Network
Device Naming rather than traditional "ethX" naming, and this causes a
number of installation problems, particularly in the use of ksdevice= (RH)
and netdevice= (Suse) on the kernel cmdline. I have not had time to
experiment much with installnic and primarynic, which is certainly the
better way to handle it; so far I've been hacking my pxeboot cfg files as a
workaround. :- (
I've seen also that installers are inconsistent in their application of
CNDN; it seems to be a "work in progress" in anaconda & autoyast. For
example, several versions of SLES12 beta were inconsistent in their
behavior on the same HW; sometimes it used CNDN and other times ethX.
A separate but related problem is similar inconsistency in NIC naming in
kickstart & autoyast files. The generated files can fail if they contain
hard-coded names that are different from what the installer is using "this
time" -- even if the installed that *generated* the file was successful.
Dave H.
On 07/10/2014 08:41 AM, Jarrod B Johnson wrote:
What happens if you leave installnic and primarynic blank? xCAT
should autodetect in that case. There's a high chance that 'eth0' is
not what you think it is and the autodetection should overcome it.
Inactive
hide details for Hellen Nyatsambo ---07/10/2014
07:26:21
AM---Hello I'm provsioning nodes with multiple
NICS. the nodHellen Nyatsambo ---07/10/2014 07:26:21 AM---Hello I'm
provsioning nodes with multiple NICS. the nodes are receiving an
From: Hellen Nyatsambo <[email protected]>
To: [email protected]
Date: 07/10/2014 07:26 AM
Subject: [xcat-user] ksdevice problem
Hello
I'm provsioning nodes with multiple NICS. the nodes are receiving an
image, after hardware initialise they fail with error "No way to
determine which NIC to use, and cannot prompt in cmdline mode.
Halting. Please use the ksdevice= parameter to specify the device
name (e.g., eth0) or the MAC address of the NIC to use for
installation."
Installnic is set to eth0 in the noderes table.
tabdump noderes
#node,servicenode,netboot,tftpserver,tftpdir,nfsserver,monserver,nfsdir,installnic,primarynic,discoverynics,cmdinterface,xcatmaster,current_osimage,next_osimage,nimserver,routenames,nameservers,proxydhcp,comments,disable
"compute",,"pxe","172.20.100.1",,"172.20.100.1",,,"eth0","eth0",,,"172.20.100.1",,,,,,,,
Where else do i need configure ksdevice. I've tried placing "ksdevice
eth0" in compute.tmpl and that didnt work.
Thanks
------------------------------------------------------------------------------
Open source business process management suite built on Java and
Eclipse
Turn processes into business applications with Bonita BPM Community
Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Open source business process management suite built on Java and
Eclipse
Turn processes into business applications with Bonita BPM Community
Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
