06-24-2013 04:53 AM
I have a Ignite Server-A and Ignite Client-B. Both are Itanium Blade 860 ci2 Servers. I have updated /etc/bootptab file on Server-A with client information. And using make_net_recovery I took the ignite backup of client-B on to the Ignite Server-A.
On Server-A. I performed the following
1. In /etc/inetd.conf to make certain bootps and tftp entries have been uncommented.
2. inetd -c restarted properly. No errors in syslog.log
3. dhcptools -v comes out without any problem.
4 .Checked the tftp line in /etc/inetd.conf to make certain /opt/ignite an /var/opt/ignite directories are listed.
/etc/bootptab file entry as below,
While restoring ignite image on client-B getting error as below,
Shell> lanboot select -dn testprofile
Profile Name: testprofile
Network Type: IPv4
Server IP address: xxx.xxx.xxx.xxx
Client IP address: xxx.xxx.xxx.xxx
Gateway IP address: xxx.xxx.xxx.xxx
Subnet Mask: 255.255.255.0
Boot File: /opt/ignite/boot/nbp.efi
M 001 PcieRoot(0x30304352)/Pci(0x3,0x0)/Pci(0x0,0x0)/MAC
M 002 PcieRoot(0x30304352)/Pci(0x3,0x0)/Pci(0x0,0x1)/MAC
M 003 PcieRoot(0x30304352)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC
M 004 PcieRoot(0x30304352)/Pci(0x4,0x0)/Pci(0x0,0x1)/MAC
Select Desired LAN: 002
Performing a directed lanboot...
PXE-E18: Server response timeout.
Solved! Go to Solution.
06-24-2013 07:38 AM
Are you sure you are booting from the correct LAN interface?
The message seems to indicate that it can't boot via the interface you chose. Have you tried choosing one of the other LAN interfaces to see if you have better luck?
06-24-2013 10:44 AM
Sure interface 002 is the correct one?
What kind of interconnect modules you are using?
Hope this helps!
There are only 10 types of people in the world -
those who understand binary, and those who don't.
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!