Hi Jarrod,

I ran the following commands:

makedhcp idpx8n004eth0 -s 'filename elilo-x64.efi'
makedhcp idpx8n042eth0 -s 'filename elilo-x64.efi'

to try to boot the nodes we're having issues with, and now see the 
following entries:

host idpx8n004eth0 {
  dynamic;
  hardware ethernet e4:1f:13:f0:32:00;
  fixed-address 172.20.129.54;
        supersede server.ddns-hostname = "idpx8n004eth0";
        supersede host-name = "idpx8n004eth0";
        supersede server.next-server = ac:14:80:14;
        supersede server.filename = "yaboot";
}
host idpx8n004eth0 {
  dynamic;
  deleted;
}
host idpx8n004eth0 {
  dynamic;
  hardware ethernet e4:1f:13:f0:32:00;
  fixed-address 172.20.129.54;
        supersede server.ddns-hostname = "idpx8n004eth0";
        supersede host-name = "idpx8n004eth0";
        supersede server.next-server = ac:14:80:14;
}
host idpx8n042eth0 {
  dynamic;
  deleted;
}
host idpx8n042eth0 {
  dynamic;
  hardware ethernet e4:1f:13:f0:3d:dc;
  fixed-address 172.20.129.92;
        supersede server.ddns-hostname = "idpx8n042eth0";
        supersede host-name = "idpx8n042eth0";
        supersede server.next-server = ac:14:80:14;
}

Is that right? 

Thanks!

Matt Newton
Emerging Technologies Solutions Development
Watson Strategic Initiatives Engineering
914-945-2196
[email protected]

"The best way to find yourself is to lose yourself in the service of 
others." – Mahatma Gandhi



From:
Jarrod B Johnson/Raleigh/IBM@IBMUS
To:
xCAT Users Mailing list <[email protected]>
Cc:
Robert W Krull/Watson/IBM@IBMUS, Gary C Sutherland/Watson/IBM@IBMUS, 
Wesley Most/Watson/IBM@IBMUS, James A Lindeman/Austin/IBM@IBMUS, Michael 
Frissora/Watson/IBM@IBMUS, Brent Wolfe/Watson/IBM@IBMUS, Abdoulaye K 
Traore/Watson/Contr/IBM@IBMUS
Date:
08/25/2011 11:14 AM
Subject:
Re: [xcat-user] elilo-x64.efi boot not setting up properly



So that was in conjunction with the 'quick fix' elilo.pm. The trick for 
keeping that was that nodeset induces a "makedhcp -s 'filename 
elilo-x64.efi'". dhcp.pm is currently oblivious.

You can as a workaround do 'makedhcp <noderasge> -s 'filename 
elilo-x64.efi'" until such time the proper uefi support comes in (with 
xnba method).

Matthew Newton---08/25/2011 11:02:50 AM---Hi, We have some iDataPlex dx360 
M3 nodes with UEFI firmware. We were

From: Matthew Newton/Watson/IBM@IBMUS
To: xCAT Users Mailing list <[email protected]>
Cc: Robert W Krull/Watson/IBM@IBMUS, Gary C Sutherland/Watson/IBM@IBMUS, 
Wesley Most/Watson/IBM@IBMUS, James A Lindeman/Austin/IBM@IBMUS, Michael 
Frissora/Watson/IBM@IBMUS, Brent Wolfe/Watson/IBM@IBMUS, Abdoulaye K 
Traore/Watson/Contr/IBM@IBMUS
Date: 08/25/2011 11:02 AM
Subject: [xcat-user] elilo-x64.efi boot not setting up properly



Hi, 

We have some iDataPlex dx360 M3 nodes with UEFI firmware. We were directed 
to use "elilo" as the netboot method in the noderes table, which is 
supposed to point it to the elilo-x64.efi entry in /tftpboot, but when we 
"makedhcp -n" and then "makedhcp -a", it creates entries such as the 
following: 

host idpx8n004eth0 { 
dynamic; 
hardware ethernet e4:1f:13:f0:32:00; 
fixed-address 172.20.129.54; 
supersede server.ddns-hostname = "idpx8n004eth0"; 
supersede host-name = "idpx8n004eth0"; 
supersede server.next-server = ac:14:80:14; 
supersede server.filename = "yaboot"; 
} 

or even in some cases: 

host idpx8n010eth0 { 
dynamic; 
hardware ethernet e4:1f:13:f0:3b:b4; 
fixed-address 172.20.129.60; 
supersede server.ddns-hostname = "idpx8n010eth0"; 
supersede host-name = "idpx8n010eth0"; 
if option vendor-class-identifier = "ScaleMP" { 
supersede server.filename = "vsmp/pxelinux.0"; 
} else { 
supersede server.filename = "pxelinux.0"; 
} 
supersede server.next-server = ac:14:80:14; 
} 

The yaboot entry is bad news because when the node is booted it tries 
loading that file and it ends up hanging the IMM adapter and we have to go 
manually power cycle it. The pxelinux.0 is less of a problem, but still 
not correct. Our noderes entries look like this: 

[root@idpx1mgr ~]# tabdump noderes|egrep 'idpx8n004|idpx8n010' 
"idpx8n004eth0",,"elilo","172.20.128.20","172.20.128.20",,,,,,,"172.20.128.20",,,,,,
 

"idpx8n010eth0",,"elilo","172.20.128.20","172.20.128.20",,,,,,,"172.20.128.20",,,,,,
 

[root@idpx1mgr ~]# 

Can someone point us in the right direction here, so that we end up 
loading the correct (elilo-x64.efi) file on PXE boot? 

Thanks!

Matt Newton
Emerging Technologies Solutions Development
Watson Strategic Initiatives Engineering
914-945-2196
[email protected]

"The best way to find yourself is to lose yourself in the service of 
others." – Mahatma Gandhi 
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user



<<image/gif>>

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to