boot lan.ip-address install

[Jun Zhang_4]

So far I've never succeeded in doing this at a client's firmware prompt, Main Menu: Enter command or munu>
search lan install ENTER
Error: Unknown device
boot lan.ip-address install ENTER
Not a boot device
boot 60/6.0.ip-address install
booting....
This will be forever, I have to press the power button to get back to a point.
I have a ignite server with a know ip-address, pushing from server is fine. Only this pulling doesn't work for me.


Jun Z

[Leif Halvarsson_2]

Hi,
I assume you have installed an Ignite server. Have you added any IP-adresses for booting on the Tgnite server.

[Bernhard Mueller]

Hi,

this HW path looks like quite an old machine, maybe lan boot is not supported for it, you might want to check in the Ignite Release Notes.

If it is supported you need to have either a DHCP server in that same subnet or on your ignite server (in the same subnet) you need to have a free IP address added in /etc/opt/ignite/instl_boottab and have instl_bootpd and tftp enabled in /etc/inetd.conf.

Regards,
Bernhard

[Steven E. Protter]

instl_adm -d make sure everything is good.

lanadmin -x 0


make sure speed and duplex is consistent at both NIC cards and the network switch. Auto Negotiate should NOT be used in any of the three configurations I mentioned. Configuration must be explicit

To monitor whats going on while you try this, take the following steps:

tail -f /var/adm/syslog/syslog.log

netstat -i 0

That will show you if any bytes are getting through.

Try and post results. It is likely that you'll find and correct the problem without having to post again.

the tail -f on syslog really helps you see if the packets are getting through.

I suppose bad cables could also cause this, but its not likely.

SEP

[Scot Bean]

Here's another command from the firmware prompt that can help diagnose lanboot problems, try

SEARCH LAN INSTALL

This pings the LAN for ignite servers.

The point made about old machines is valid. However, old firmware could also be blocking you. Check to see if you have the latest firmware, also.

[Julian Perez_1]

Hello,

This type of behavior is seen on both N and L class systems, yet they are able to boot fine from the IUX server The systems do not recognize the IUX server in a 'search lan'.

Maybe this is your case.

Also take into account that the only interfaces supported for doing a client network boot from a server are the built-in ethernet (10-Base-T, and 100-Base-T) on all newer system models. The T, V, H, G, I, E class and 9000/8*7S systems do not support network boot. At least this is last information I had.

There are several important points to check in this case. For example:

1) On the Ignite server, verify that these entries exist as a minimum in /etc/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

2) Check to make sure the temporary IP addresses used during the client install are available and configured in /etc/opt/ignite/instl_boottab. Use the documentation in the file to verify the format of the entries and that this IP address will be available to the client.

3) Verify the INSTALLFS config file by running instl_adm â d. At a minimum, it should correctly describe the serverâ s IP address, netmask, gateway address and default route.

As you can see, there is several and not easy points to check. Fro this reason, before them, make sure the network card being used to boot the client is supported for network boot. See the network interface support matrix in the Ignite release notes under Version History at:

http://www.software.hp.com/products/IUX/infolib.html

In this link there is also a lot of information that maybe can help to you.

Have a nice day!

[Jun Zhang_4]

Thank you all for the replies.
-in /inetd.conf
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd
-in /etc/services
instl_boots 1067/udp # installation bootstrap protocol server
instl_bootc 1068/udp # installation bootstrap protocol client
lanadmin -x 0
Current Config = 100 Full-Duplex AUTONEG
-This option (-x) is not supported on my E35, which have the current firmware version 1.3.
-Two ip addresses are listed in /etc/opt/ignite/instl_boottab
-/opt/ignite/share/doc/FAQ hinted that E class is supported by both Ignite A and B. My Ingite version is B.4.4.29.
-Content of instl_adm -d
server="159.66.144.146"
netmask[]="0xffffff00"
route_gateway[0]="159.66.144.10"
route_destination[0]="default"
# end instl_adm defaults.
disable_dhcp=true
run_ui=true
control_from_server=false
-sea lan install generated
Error: Unknown device

Jun Z

[Steven E. Protter]

RED FLAG !!!!!

Current Config = 100 Full-Duplex AUTONEG

This can be the entier cause of your problem.

You want to be:

Current Config = 100 Full-Duplex MANUAL

This includes switch port configuration.

Any other configuration will not be reliable and can directly cause the symptoms you are undergoing.

I'm attaching an example of /etc/rc.config.d/hpbtlanconf which will get you started.

It needs to be on server client and switch.

SEP

[Jun Zhang_4]

Steven,
Is there a command line option I can use to change the interface to MANUAL?

Jun Z

[Jun Zhang_4]

At ignite server:
lanadmin -x 0
Current Config = 10 Half-Duplex MANUAL
At client firmware prompt:
search lan install
Error: Unknown device
boot lan.ip-address install
Error: Not a boot path
I had a feel that there is no communication yes between the E35 client and any others on the network.

Jun Z

[Christopher Rupnik]

Hi there,
There is no lan boot support for ignite on E-class machines. There is the ability to do MOP boots for specific HP only maintenance, however, ignite will not be able to boot a kernel off the network.

Two ways around that however, are to use a bootable CDROM and then load the image from the ignite server, or use a bootable tape.

Good luck either way, but there is no need to continue down this current path.