Okay, thanks for the explanation. Cheers, Josh
On Wed, Jul 25, 2012 at 2:28 PM, Jarrod B Johnson <jbjoh...@us.ibm.com>wrote: > So the issue is that the xnba can work fine. The problem is the linux > image that subsequently loads lacked the driver update. In an ideal world, > we make an efi executable that does everything in UEFI that is moderately > future proof. In a practical world we work with the much richer linux > toolset for lack of time to develop EFI resources. > > -----Josh Nielsen <jniel...@hudsonalpha.com> <jniel...@hudsonalpha.com>wrote: > ----- > > To: xCAT Users Mailing list > <xcat-user@lists.sourceforge.net><xcat-user@lists.sourceforge.net> > From: Josh Nielsen <jniel...@hudsonalpha.com> <jniel...@hudsonalpha.com> > Date: 07/25/2012 02:58PM > Subject: Re: [xcat-user] Getdestiny failing - can't open '/tmp/dhcpserver' > > Thanks for the information Lissa. > > I do have another more general question as well though. It is regarding > the xnba boot image itself, which appears to be based off of gPXE. The idea > of gPXE is that it is UNDI-capable and does not have to use TFTP to serve > the images correct? And looking at the xnba.kpxe image/bootloader extension > of '.kpxe' it looks like that is reserved specifically for images that load > UNDI but offload PXE. According to this page ( > http://etherboot.org/wiki/gpxe_imagetypes) the extensions for images > break down like this: > > - .pxe is an image designed to be chainloaded, unloading both the > underlying PXE and UNDI code sections. > - .kpxe is a PXE image that keeps UNDI loaded and unloads PXE > - .kkpxe is a PXE image that keeps PXE+UNDI loaded and return to PXE > (instead of int 18h). > > So does xnba.kpxe try to interact with the NIC card via UNDI once it > loads? If so since UNDI is an abstracted API, and unless the API has been > updated on the newer NIC cards, shouldn't it work with just about any > network card regardless? From this PXE chainloading page ( > http://etherboot.org/wiki/pxechaining) it says: > > "When chainloading gPXE from PXE, gPXE can use this API (instead of > loading an hardware driver). This way, you're getting support for network > controllers that are not natively supported by gPXE. Some network > controllers have improved performance when using the UNDI driver over the > vendor specific gPXE driver." > I'm just curious about some of the theory behind this because I'm only > used to good ol' legacy PXE. All this gPXE and UNDI stuff is new to me. > > > On Wed, Jul 25, 2012 at 12:57 PM, Lissa Valletta <lis...@us.ibm.com>wrote: > >> >> Version 2.3.x has not been supported for a long time. You need to be on >> the latest level of 2.6 for support , but you might as well go to the >> latest release which is 2.7.3. You can upgrade xCAT and stay at your >> current Centos level. >> >> Lissa K. Valletta >> 2-3/T12 >> Poughkeepsie, NY 12601 >> (tie 293) 433-3102 >> >> >> >> Josh Nielsen ---07/25/2012 01:33:25 PM---Hello, I have some new IBM >> System X DX360M4 nodes (all our previous ones were >> >> From: Josh Nielsen <jniel...@hudsonalpha.com> >> To: xcat-user@lists.sourceforge.net >> Date: 07/25/2012 01:33 PM >> Subject: [xcat-user] Getdestiny failing - can't open '/tmp/dhcpserver' >> >> ------------------------------ >> >> >> >> Hello, >> I have some new IBM System X DX360M4 nodes (all our previous ones were >> DX360M3s) that I am trying to autodiscover with xCAT and I am running into >> the same problem as in this mail thread: * >> http://www.mail-archive.com/xcat-user@lists.sourceforge.net/msg01267.html >> *<http://www.mail-archive.com/xcat-user@lists.sourceforge.net/msg01267.html>. >> Essentially the node boots up, does a dhcpdiscover, and grabs a generic >> bootloader (in my case yaboot but it also works with pxelinux.0) which then >> reinitiates the dhcpdiscover and queries again for the appropriate >> bootloader from the file in the xcat/xnba/nets/ folder and is served & >> boots xnba.kpxe. At this point I believe the xnba image is supposed to load >> and execute the autodiscovery process which includes the getdestiny script, >> but all I am seeing are the messages: >> >> cat: can't open '/tmp/dhcpserver': No such file or directory >> grep: /tmp/destiny: No such file or directory >> grep: /tmp/destiny: No such file or directory >> >> One reply by Jarrod Johnson to that email thread above mentioned a >> possible network driver issue and suggested using Genesis from xCAT >> v2.7. According to 'xcatconfig -v' I am running Version 2.3.1 of xCAT and I >> am running on Centos 5 (2.6.18-128.el5). Is there a way to get this working >> with my current version of xCAT and OS (inject drivers somehow?), or do I >> need to update to v2.7 of xCAT (does that require Centos 6)? In any case, >> is a network driver the most likely explanation for what I am seeing? I >> have tried everything that I can think of from the switch side to make sure >> SNMP is enabled and the port definitions are correct in the switch table >> for autodiscovery. Any ideas? >> >> Thanks, >> Josh Nielsen >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> xCAT-user mailing list >> xCAT-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/xcat-user >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> xCAT-user mailing list >> xCAT-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/xcat-user >> >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user > >
<<Image.1__=0ABBF0D5DFF32E098f9e8a93df938@us.ibm.com.gif>>
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
