Can't boot lan to Ignite server

[Denise DeKeuster]

I created an golden image of one of my systems and use this to ignite the rest of my workstations (C3600). As I was in the process of igniting one workstation, the workstation with the image on it was not found, so the process died. When I try to boot lan.xxx install, the system can't find my ignite server. The server was never set-up with a depot because I always use my image. It is also on a different subnet than the dead system. How can I boot the dead system and install my image from my ignite server? What needs to be set-up on my server?

[Patrick Wallek]

In order to boot your workstation from an Ignite/UX server on a different subnet you must set up a 'boot helper' system on the same subnet as your workstation.

Instructions for doing this can be found in the Ignite/UX administrators guide here:
http://docs.hp.com/hpux/onlinedocs/B2355-90810/B2355-90810.html

Look in the section "Using a Boot-Helper System "

Good luck.

[Tim Adamson_1]

You definitely need a boot helper if you are on a different subnet.

The Ignite-UX Admin Guide (available at www.docs.hp.com) shows you how to set this up. Refer to Appendix B (I think)

The boot helper does work as I use it myself.


Tim.

[Steven E. Protter]

Another helpful(helpless?) hint.

On the target server, just prior to connect attempt:

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

When you attempt a connect you should see it happen in real time there. If not, you still don't have the boot helper working right or have other network issues.

lanadmin -x 0

Shows the speed and duplex of NIC cards, it may need to be hardcoded, especially in a Cisco environment.

See file /etc/rc.config.d/hpbtlanconf

Any Cisco hardware that connects with HP NIC's that are NOT 1000 BaseT should be set to manual, not autonegotiate.

SEP