I changed installnic and primarynic to em1 and it works ok now. Thank
you all
--
___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lis
also from node to node (which
CNDN breaks pretty thoroughly).
From: deheller
To: xcat-user@lists.sourceforge.net
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 tradit
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
To: xcat-user@lists.sourceforge.net
Date: 07/10/2014 07:26 AM
Subject: [xcat-user] ksdevice problem
---
7/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.
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) o
