Boot over ignite

[Ignite_2]

Hello,

I have an issue, when installing rx6600 from ignite server. The steps I did are following:
- create install profile
- run lanboot command
- then I get error message:
* Bringing up Network (lan0)
* running: lanadmin -X 100FD 0
Unable to open catalog for C
Switching to the use of Internal Messages.
WARNING: The link settings you have specified for this card
must match the settings of its link partner.

add net default: gateway 10.151.144.1
* Reading configuration information from server...

* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>

It seems, that there isn't problem with INDEX file or lan settings, because new server can connect to Ignite.

On ignite I've following entry for tftp:

tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite

Can you please help to fix my problem?

[Steven E. Protter · Accepted solution]

Shalom,

* running: lanadmin -X 100FD 0

That system has a 1000 BaseT card and should auto negotiate to that speed. The switch ports on the lan router, should be configured to auto negotiate.

Itanium systems will go out and seek the Ignite server if its on the same subnet. They will find it automagically.

On the Ignite server, three things need to be configured in inetd.conf


tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd


Also,
"/etc/opt/ignite/instl_boottab"
Needs boot entries.

Example:
192.8.125.151:0x0018FE2F0241::reserve
192.8.125.185:0x0018FE2F0249::reserve


The second entry is the MAC address of the NIC card that is booting.

Lots of fun stuff to check.

SEP

[Ignite_2]

Thanks for response,

I've checked all settings. Also have tried to install the client using bootsys command from ignite, and it stopped at same point.

Ignite server and client has to be in same subnet?

[Torsten.]

Do you see related entries in the ignite servers logs? Just in case your client connects to the correct machine...

Consider to use the dbprofile option from clients EFI shell.

[Ignite_2]

The dbprofile option I have used had the same result as bootsys. When running any of these commands, I'm watching the syslog.log on ignite server, but there isn't any message related to installation.

[Torsten.]

With dbprofile you can do installations even across subnets. Somehow I think you maybe still have a config problem or you hit the wrong target.

[Ignite_2]

OK, I've checked the settings again and will re-try dbprofile. In /etc/inetd.conf are all 3 entries uncommented. But in /etc/bootptab isn't any entry related to this installation.

Should I update this file with MAC address of client which should be installed?

Thank you

[Ignite_2]

Hmm... even if I added entry into bootptab it doesn't work,

[Steven E. Protter]

Shalom again,

don't forget to kill and restart inetd.

inetd -k
inetd
# must be root.

Are the systems on the same subnet? if not you may need an Ignite boot helper.

There should be log files to assist in diagnosis.

if a firewall is between the systems all required ports (see /etc/services) must be open.

SEP