I have established that there are no problems with the NIC in the machines.
I am still having the problem of the clonezilla image not picking up a dhcp address for eth0 when the linux image boots.
The client DOES get a dhcp address during the PXE boot sequence and successfully launches the DRBL menu, and the image session that I have created shows up for all the test computers in the drbl menu.
However, when the image session is selected and the system begins to boot (presumably using the clonezilla image) so that the save or restore session can be started, the dhcp never successfully gets an IP address.
Below is the syslog messages for the dhcpd server startup:
Nov 15 09:40:37 epsilon10 dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 15 09:40:37 epsilon10 dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 15 09:40:37 epsilon10 dhcpd: All rights reserved.
Nov 15 09:40:37 epsilon10 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 15 09:40:37 epsilon10 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Nov 15 09:40:37 epsilon10 dhcpd: data: hardware: raw packet not available
Nov 15 09:40:39 epsilon10 dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 15 09:40:39 epsilon10 dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 15 09:40:39 epsilon10 dhcpd: All rights reserved.
Nov 15 09:40:39 epsilon10 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 15 09:40:39 epsilon10 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Nov 15 09:40:39 epsilon10 dhcpd: data: hardware: raw packet not available
Nov 15 09:40:39 epsilon10 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Nov 15 09:40:39 epsilon10 dhcpd: data: hardware: raw packet not available
Nov 15 09:40:39 epsilon10 dhcpd: Wrote 0 deleted host decls to leases file.
Nov 15 09:40:39 epsilon10 dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 15 09:40:39 epsilon10 dhcpd: Wrote 0 leases to leases file.
Then syslog messages for the clients as they boot via PXE into the drbl system:
Client 1:
Nov 15 09:45:20 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:17 via eth0: network 192.168.0/24: no free leases
Nov 15 09:45:20 epsilon10 dhcpd: Client 0:17:31:54:62:17 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:20 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:17 via eth0
Nov 15 09:45:20 epsilon10 dhcpd: DHCPOFFER on 192.168.0.13 to 00:17:31:54:62:17 via eth0
Nov 15 09:45:22 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.13 (134.117.28.9) from 00:17:31:54:62:17 via eth0: unknown lease 192.168.0.13.
Nov 15 09:45:22 epsilon10 dhcpd: Client 0:17:31:54:62:17 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:22 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.13 (134.117.28.9) from 00:17:31:54:62:17 via eth0
Nov 15 09:45:22 epsilon10 dhcpd: DHCPACK on 192.168.0.13 to 00:17:31:54:62:17 via eth0
Nov 15 09:45:22 epsilon10 in.tftpd[25965]: tftp: client does not accept options
Client 2:
Nov 15 09:45:36 epsilon10 dhcpd: Client 0:17:31:54:62:10 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:36 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:10 via eth0
Nov 15 09:45:36 epsilon10 dhcpd: DHCPOFFER on 192.168.0.14 to 00:17:31:54:62:10 via eth0
Nov 15 09:45:36 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:10 via eth0: network 192.168.0/24: no free leases
Nov 15 09:45:38 epsilon10 dhcpd: Client 0:17:31:54:62:10 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:38 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.14 (134.117.28.9) from 00:17:31:54:62:10 via eth0
Nov 15 09:45:38 epsilon10 dhcpd: DHCPACK on 192.168.0.14 to 00:17:31:54:62:10 via eth0
Nov 15 09:45:38 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.14 (134.117.28.9) from 00:17:31:54:62:10 via eth0: unknown lease 192.168.0.14.
Nov 15 09:45:38 epsilon10 in.tftpd[25974]: tftp: client does not accept options
Client 3:
Nov 15 09:45:48 epsilon10 dhcpd: Client 0:17:31:54:61:74 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:48 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:61:74 via eth0
Nov 15 09:45:48 epsilon10 dhcpd: DHCPOFFER on 192.168.0.15 to 00:17:31:54:61:74 via eth0
Nov 15 09:45:48 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:61:74 via eth0: network 192.168.0/24: no free leases
Nov 15 09:45:50 epsilon10 dhcpd: Client 0:17:31:54:61:74 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:50 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.15 (134.117.28.9) from 00:17:31:54:61:74 via eth0
Nov 15 09:45:50 epsilon10 dhcpd: DHCPACK on 192.168.0.15 to 00:17:31:54:61:74 via eth0
Nov 15 09:45:50 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.15 (134.117.28.9) from 00:17:31:54:61:74 via eth0: unknown lease 192.168.0.15.
Nov 15 09:45:50 epsilon10 in.tftpd[25983]: tftp: client does not accept options
There are NOT any syslog messages for when the client tries to get a dhcp address once the clonezilla session has been started, which implies the messages are not even getting through to my drbl/dhcpd server. It tries 3 times to acquire a dhcp address and then finally fails completely.
I have also notice that there are no leases being generated in /var/lib/dhcp/dhcpd.leases file (even during the PXE/DRBL boot phase when I KNOW that the clients are being given their correct addresses... because they appear on the screen)
So, questions:
1) Any ideas on why leases are not showing up? Did drbl move the default location for lease reporting?
2) Any ideas on why dhcp is working for the PXE/drbl boot, but not for the follow-up clonezilla session launch?
Thanks for the help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To answer your questions:
No, drbl uses the DHCP packages from your GNU/Linux distribution. The reason it did not write in the lease files maybe is because your client does not send dhcp client request successfully to your drbl server. Why ? Good question. One of the possibilities is your network card is up later. You can try to let your DRBL client send dhcp request much more time by doing this in the DRBL server like this:
/opt/drbl/sbin/mknic-nbi -r 10 -p 3
For more info about mknic-nbi, check "/opt/drbl/sbin/mknic-nbi --help"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a follow-up to the previous post:
http://sourceforge.net/forum/forum.php?thread_id=1865032&forum_id=394751
I have established that there are no problems with the NIC in the machines.
I am still having the problem of the clonezilla image not picking up a dhcp address for eth0 when the linux image boots.
The client DOES get a dhcp address during the PXE boot sequence and successfully launches the DRBL menu, and the image session that I have created shows up for all the test computers in the drbl menu.
However, when the image session is selected and the system begins to boot (presumably using the clonezilla image) so that the save or restore session can be started, the dhcp never successfully gets an IP address.
Below is the syslog messages for the dhcpd server startup:
Nov 15 09:40:37 epsilon10 dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 15 09:40:37 epsilon10 dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 15 09:40:37 epsilon10 dhcpd: All rights reserved.
Nov 15 09:40:37 epsilon10 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 15 09:40:37 epsilon10 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Nov 15 09:40:37 epsilon10 dhcpd: data: hardware: raw packet not available
Nov 15 09:40:39 epsilon10 dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 15 09:40:39 epsilon10 dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 15 09:40:39 epsilon10 dhcpd: All rights reserved.
Nov 15 09:40:39 epsilon10 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 15 09:40:39 epsilon10 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Nov 15 09:40:39 epsilon10 dhcpd: data: hardware: raw packet not available
Nov 15 09:40:39 epsilon10 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Nov 15 09:40:39 epsilon10 dhcpd: data: hardware: raw packet not available
Nov 15 09:40:39 epsilon10 dhcpd: Wrote 0 deleted host decls to leases file.
Nov 15 09:40:39 epsilon10 dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 15 09:40:39 epsilon10 dhcpd: Wrote 0 leases to leases file.
Then syslog messages for the clients as they boot via PXE into the drbl system:
Client 1:
Nov 15 09:45:20 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:17 via eth0: network 192.168.0/24: no free leases
Nov 15 09:45:20 epsilon10 dhcpd: Client 0:17:31:54:62:17 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:20 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:17 via eth0
Nov 15 09:45:20 epsilon10 dhcpd: DHCPOFFER on 192.168.0.13 to 00:17:31:54:62:17 via eth0
Nov 15 09:45:22 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.13 (134.117.28.9) from 00:17:31:54:62:17 via eth0: unknown lease 192.168.0.13.
Nov 15 09:45:22 epsilon10 dhcpd: Client 0:17:31:54:62:17 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:22 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.13 (134.117.28.9) from 00:17:31:54:62:17 via eth0
Nov 15 09:45:22 epsilon10 dhcpd: DHCPACK on 192.168.0.13 to 00:17:31:54:62:17 via eth0
Nov 15 09:45:22 epsilon10 in.tftpd[25965]: tftp: client does not accept options
Client 2:
Nov 15 09:45:36 epsilon10 dhcpd: Client 0:17:31:54:62:10 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:36 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:10 via eth0
Nov 15 09:45:36 epsilon10 dhcpd: DHCPOFFER on 192.168.0.14 to 00:17:31:54:62:10 via eth0
Nov 15 09:45:36 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:62:10 via eth0: network 192.168.0/24: no free leases
Nov 15 09:45:38 epsilon10 dhcpd: Client 0:17:31:54:62:10 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:38 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.14 (134.117.28.9) from 00:17:31:54:62:10 via eth0
Nov 15 09:45:38 epsilon10 dhcpd: DHCPACK on 192.168.0.14 to 00:17:31:54:62:10 via eth0
Nov 15 09:45:38 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.14 (134.117.28.9) from 00:17:31:54:62:10 via eth0: unknown lease 192.168.0.14.
Nov 15 09:45:38 epsilon10 in.tftpd[25974]: tftp: client does not accept options
Client 3:
Nov 15 09:45:48 epsilon10 dhcpd: Client 0:17:31:54:61:74 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:48 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:61:74 via eth0
Nov 15 09:45:48 epsilon10 dhcpd: DHCPOFFER on 192.168.0.15 to 00:17:31:54:61:74 via eth0
Nov 15 09:45:48 epsilon10 dhcpd: DHCPDISCOVER from 00:17:31:54:61:74 via eth0: network 192.168.0/24: no free leases
Nov 15 09:45:50 epsilon10 dhcpd: Client 0:17:31:54:61:74 requests 1:2:3:4:5:6:b:c:d:f:10:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Nov 15 09:45:50 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.15 (134.117.28.9) from 00:17:31:54:61:74 via eth0
Nov 15 09:45:50 epsilon10 dhcpd: DHCPACK on 192.168.0.15 to 00:17:31:54:61:74 via eth0
Nov 15 09:45:50 epsilon10 dhcpd: DHCPREQUEST for 192.168.0.15 (134.117.28.9) from 00:17:31:54:61:74 via eth0: unknown lease 192.168.0.15.
Nov 15 09:45:50 epsilon10 in.tftpd[25983]: tftp: client does not accept options
There are NOT any syslog messages for when the client tries to get a dhcp address once the clonezilla session has been started, which implies the messages are not even getting through to my drbl/dhcpd server. It tries 3 times to acquire a dhcp address and then finally fails completely.
I have also notice that there are no leases being generated in /var/lib/dhcp/dhcpd.leases file (even during the PXE/DRBL boot phase when I KNOW that the clients are being given their correct addresses... because they appear on the screen)
So, questions:
1) Any ideas on why leases are not showing up? Did drbl move the default location for lease reporting?
2) Any ideas on why dhcp is working for the PXE/drbl boot, but not for the follow-up clonezilla session launch?
Thanks for the help!
To answer your questions:
No, drbl uses the DHCP packages from your GNU/Linux distribution. The reason it did not write in the lease files maybe is because your client does not send dhcp client request successfully to your drbl server. Why ? Good question. One of the possibilities is your network card is up later. You can try to let your DRBL client send dhcp request much more time by doing this in the DRBL server like this:
/opt/drbl/sbin/mknic-nbi -r 10 -p 3
For more info about mknic-nbi, check "/opt/drbl/sbin/mknic-nbi --help"