1834152 Members
2574 Online
110064 Solutions
New Discussion

Lan boot/install problem

 
SOLVED
Go to solution
Ryan Hurst
Frequent Advisor

Lan boot/install problem

Ok, I have successfully made and restored a raven system (c110) using ignite. To do this, I made the net recovery using the ignite gui. To restore I did a "bo lan. install" and it worked great.
Now I am trying to do it with an allegro system in the same way. I successfully made a network recovery archive of the allegro, but the "bo lan. install" command dosn't work at all. I then did "sea lan install" and found some other system, but not my ignite server. If I do the same command on the raven system, both the other system AND my ignite server show.
The raven, the allegro, and my ignite server are ALL plugged into the same hub. The other system is somewhere else on the network.
My question is: Why can't the allegro see the ignite server, while the raven can? Also, how do I fix this?
22 REPLIES 22
Wilfred Chau_1
Respected Contributor

Re: Lan boot/install problem

Are the client and the ignite server on the same subnet?

If not, you need to configure a boot helper. See link below.

http://www.software.hp.com/products/IUX/docs/sysadm.html#Chapter-6
Ravi_8
Honored Contributor

Re: Lan boot/install problem

Hi,

looks like machine allegro is on different subnet, whereas raven and ignite server are on same subnet.
if the client is on different subnet then a boot helper needs to be setup. look at this URL:
http://www.software.hp.com/products/IUX/docs/sysadm.html#Chapter-6
never give up
Sergejs Svitnevs
Honored Contributor

Re: Lan boot/install problem

Are you sure this hub is not a switch with different VLANs? If yes, try to change the patch cord (ignite server -- allegro).

Regards,
Sergejs
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Wilfred and Ravi:
How would I tell if the client that is in the boot console handler is on a particular subnet? I just plugged it into the switch (sorry I said hub at first, I should have made the distinction) along with the server and the working raven client. As I said before, both the working raven client and the non working allegro client can see another ignite server, but only the raven can see MY ignite server. If it helps, I'll mention that both MY ignite server and the other ignite server are on the same subnet.
Sergejs:
You're right, it is a switch, not a hub, I should have mentioned that. However, I don't belive that there are any different Vlans involved. I just powered up the switch and plugged the server and the two clients into it, as well as the lan-drop that goes to the rest of the company's network.

Thanks everybody, I eagerly await your reply!
Ravi_8
Honored Contributor

Re: Lan boot/install problem

Hi,

can you post #ifconfig lanx (x is interface number) command output of both the machines, raven and allegro
never give up
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Output from ifconfig...

working raven client:
lan0: flags=843
inet 150.1.10.16 netmask ffff0000 broadcast 150.1.255.255

nonworking allegro client:
lan0: flags=863
inet 150.1.10.11 netmask ffff0000 broadcast 150.1.255.255
Ravi_8
Honored Contributor

Re: Lan boot/install problem

Hi,

can the ignite server can see allegro (try to push s/w from ignite server into allegro)
never give up
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

I'm not sure what exactly you're asking me to do, but if you mean can I ping and telnet etc. from the server to the client, then yes.
Michael Duthie
Trusted Contributor

Re: Lan boot/install problem

pretty basic I know, but just to rule out the switch. Have you tried swapping Raven & Allegro connections at the swith over.
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

It's ok, in some areas, my knowledge is pretty basic as well.
Yes, I tried swapping the connections, it made no difference.
John Dvorchak
Honored Contributor

Re: Lan boot/install problem

This one looks like it would be easy but I gues it's not. The only hint I can give is from the man bootpd page and maybe this would apply to the Ignite server's configuration. So check /etc/dhcpdeny and /etc/bootptab files. Remember when you setup up and Ignite server it functions as a dhcp/bootp server as well:

When bootpd receives a DHCP/BOOTP request, it first checks if the
hardware address of the client is listed in the /etc/dhcpdeny
database. If yes, this client is denied lease. If the client is not
listed in the dhcpdeny database, it checks whether the client
information is in the /etc/bootptab database. If the client
information is available, bootpd sends back the reply. Otherwise, it
checks whether there is any matched relay information for the client
in the /etc/bootptab database. If so, bootpd goes through a series of
checks to see if it should relay the request. If no matched relay
information was found, bootpd checks whether the client information is
matched by a pool or device group in the /etc/dhcptab database. If a
match is found, bootpd sends back a reply. The request is dropped if
no matched group information is found.
If it has wheels or a skirt, you can't afford it.
John Dvorchak
Honored Contributor

Re: Lan boot/install problem

One other thought, when you run Ignite from the Ignite server, does allegro show up in the list of clients? If not try adding it first.
If it has wheels or a skirt, you can't afford it.
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Yes, I've added and made a network archive of the allegro client on my ignite server. I'm still working with the info from your previous post...
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Ok, there aren't any dhcp related files since dhcp isn't configured on my server. The bootptab file had the following entries in it:

ignite-defaults: ht=ethernet: hn: bf=/opt/ignite/boot/nbp.efi: bs=48
System-IPF: tc=ignite-defaults: ha=00d009000000: ip=190.40.101.22: sm=255.255.248.0: gw=190.1.48.1: ds=190.1.48.11

I tried adding an entry specific to my wayward client. It didn't change anything.
Michael Duthie
Trusted Contributor

Re: Lan boot/install problem

strange indeed !

How far does "bo lan. install" get ?
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Mike:
I successfully made a network recovery archive of the allegro, but the "bo lan. install" command dosn't work at all.
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Mike:
I guess I should clarify...
After hitting enter and answering "n" to the interact with ipl question, it tries to boot for a minute or so and times out, being unable to find a "nonexistant device".
Wilfred Chau_1
Respected Contributor

Re: Lan boot/install problem

What is the subnet for your ignite server? Is lan0 on 150.1.10.0 as well?

All subnet has to be the same and also they should all use lan0, or the primary lan.
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Yes, all of them are on the same subnet. This network is relatively small and unsophisticated. They are all connected through thier built in NICs at lan0.
Wilfred Chau_1
Respected Contributor

Re: Lan boot/install problem

try this:

on the client system,
create a .rhost file and add to it the ignite server.

then on the server system,
do this:

# /opt/ignite/bin/bootsys -w -v

See if the above works or not.
I am doing a push rather than a pull.
Anders Gullberg
Frequent Advisor
Solution

Re: Lan boot/install problem

Hi,

Have you an entry in the /etc/opt/ignite/instl_boottab on the server?
I guess you need to have an address ther to get a temporaray ip address.

Regards Anders
Ryan Hurst
Frequent Advisor

Re: Lan boot/install problem

Thank you, Anders!
After adding an "IP address usable by any client" to the ignite boottab file, It showed right up on the "sea lan install" command and I am now attempting a restore! Thanks!!!