Ignite

[Shoyru]

I have a user who can't ignite/boot her B180 controller from our ignite server. We can see our ignite server when we run "sea lan install". This is despite we tried changing to another controller. The error message is The error message is:
Failed I/O operation with
ENTRY_IO
Status = -3

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000010 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 004A0320 00000000 00000000 00000000 00000000 00000000

Error Reading IPL

Could someone please advice? Thanks!

[Bernhard Mueller]

Lauren,

that is all I could find on "Status = -3":


Can not complete call without error. An error of unknown type prevented the call from completing correctly


anyway it seems your problem might be on the ignite server side, is it setup correctly in /etc/inetd.conf?, tftp enabled?, can you try with another box?

Regards,
Bernhard

[Kevin O'Donovan]

Hi,

that sounds familiar, but its a little while back. It came down to MAC addresses. In the startup scripts the MAC address was being changed in the server I was trying to boot from the Ignite server.

So when it was up and running and did the backup to the Ignite server it had a different MAC address to when it had just got to the IPL and went to try to boot from the Ignite server. The Ignite server only associated the backup with a particular MAC address so didn't put the 2 together when I tried to boot.

It was actually HP who put in the change of MAC address into the server, it came that way, never found out why.

So, check if that is the case, I think its in the /etc/rc.config.d/netconf file where the MAC address can be changed at boot time.

hope that helps,
Kevin.

[Bernhard Mueller]

Kevin,

excellent hint!

To find out the changed MAC do:
grep "STATION_ADDRESS.*=" /etc/rc.config.d/hp*

Regards,
Bernhard

[Steven E. Protter]

There is a networking problem between the machine you are trying to boot and the server.

Make sure both machines are using their built in lan.

Make sure networking speed is what you expect:
lanadmin -x 0

If the built in is lan 0

Even if there are not obvious issues, consider hard coding your network settings into /etc/rc.config.d/hpbtlanconf, especially if you are using a cisco switch.

For LAN cards below 1000 BaseT the switch must be set up explicit, and not auto negotiate.

You can't boot an Ignite client off an add in lan. You can boot off of add in and do the transfer on the add in, no problem with that.

On the server, ps -ef | grep boot a few times before the Ignite boot and then during. In another window if possible, tail -f /var/adm/syslog/syslog.log

Its nice to see it blow up real time.

SEP

[Shoyru]

Those are wonderful possible solutions, everyone! I am so glad to have every input to my problem...Thank you very much! Pls allow me to do several testings with my users and hopefully, we do this right together! Will be back with the good news! :)