sea lan install - no devices found

[Ramones]

Hi

I am trying to install a machine with ignite server.
I've configured in the ignite server the /etc/bootptab file with ha (MAC address) and client ip options, like this:
myserver:\
tc=ignite-defaults:\
ip=xxx.xx.xxx.xx:\
ha=001185AF74B0
Then I've tried to boot from the client's console with "boot lan [server IP address] install" and gives an error
Then I made sea lan install to see if the client would find some server to talk to...and I got "no devices found" . Now what? :-)


Thanks
R

[Scot Bean]

You have a PA-RISC client and have setup a server setting for an Itanium client.

Unfortunately, the two use different bootp protocols.

/etc/bootptab is for Itanium booting. It will not help you with this PA-RISC client.

Your PA-RISC client must be on the same subnet as your Ignite server for boot lan.ipaddress install to work.

You may find this whitepaper helpful on Ignite booting: http://docs.hp.com/en/5992-5274/5992-5274.pdf

[Ramones]

Hi

I've configured the client IP and MAC address right, in /etc/opt/ignite/instl_boottab (i've realized the error just after opening the thread).

I moved the client to the same vlan of the server but I am getting the same error.

Any ideas?
Thanks,
R

[Scot Bean]

See if /etc/inetd.conf has the bootp ignite entry, look in the /var/adm/syslog/syslog.log on the server, see if any errors there.

The white paper has some troubleshooting tips also.

[Michael Steele_2]

Hi

verify the client's mac address on the client server.

verify the client's backup image under its mac address on the ignite server

[Kapil Jha]

You will have to check if bootp and tftp is enable in indetd.conf.

What is the error you got.

BR,
Kapil+

[Ramones]

Hi

I've configured all right I believe.
- I have this entry in /etc/inetd.conf
"bootps dgram udp wait root /usr/lbin/bootpd bootpd"
- I have an entry in /etc/opt/ignite/instl_boottab like "client_IP_address:client_MAC_address::reserve" (with the leading 0x in the MAC Address)
- I give this command in the client's console after I interrupt boot process:
"boot lan.server_IP_address install"

The error is:

Booting...
Failed to initialize with ENTRY_INIT Status = -4


0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
3 0 0 0
0 0 0 0
8 0 0 0
0 0 0 0
.... FAILED.

Any ideas?

Thanks,
R

[Shane Seymour]

I would strongly suggest reading what Scott pointed you at. If you had you would have seen that bootpd does not use the instl_bootptab file (instl_bootd does) not would it reply to a bootp broadcast sent out on port 1067 (which the install option makes happen).

If you want to be able to troubleshoot this please read http://docs.hp.com/en/5992-5274/5992-5274.pdf starting on page 4.

[Ramones]

Hi

Still fighting with this...I am doing tests so it's not so bad :-)
Now, I make telnet to the instl_boots port (1067)on the server (from the client that I want to re-install with lan boot) and I get a "connection refused" message (from that client and all the machines we have...).Shouldn't I be getting some reply?

Thanks,
R

[Ramones]

And...by the way

the lan interface I'm using it´s this one:
lan 1 0/5/2/0/6/0 igelan CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter

So...I guess it's not built-in and mayyyybe that is the problem????....

Thanks,
R

[Torsten.]

Probably. What server model?

[Ramones]

Hi

9000/800/rp4440

thanks,
R

[Torsten.]

What is the PDC (firmware) version of this system?

Should be

PDC 46.34, BMC 04.06, and iLO MP E.03.32

Run sysrev from MP:

Type "SYSREV" to display system revision information. The following should be displayed if the current firmware is installed:

Current firmware revisions

MP FW : E.03.32
BMC FW : 04.06
System FW : 46.34


http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=2512015&swItem=pf-57813-1&prodNameId=401769&swEnvOID=54&swLang=13&taskId=135&mode=4&idx=0

[Torsten.]

The ethernet card matrix also says:

A9784A
PCI-X 2GB Fibre
Channel and
1000/Base-T
(copper)
(on PA-RISC);

rp4440

6 Bootable max



Your ignite server is in the same segment?


Does the client find it during a "search lan" command?

[Ramones]

Hi Torsten

Thank you for your reply.
The firmware version I have is

Current firmware revisions

MP FW : E.02.29
BMC FW : 02.37
System FW : 44.21

The client is in the same vlan of the server, but doesn't find the server with the "search lan" command.
I am only making tests with this but I am finding so much limitation in using lan boot and instaling from the server that I am starting to think that this solution is not practicable at all.
Should I upgrade firmware?
Should I give up :-)?


Thanks,
R

[Torsten.]

Before give up update the firmware!


The firmware is responsible of what the server does during this boot.

[Ramones]

Hi

I made the firmware update.
The problem persists...I don't have more ideas...


Thanks,
R

[Ranveer]

Hi
Not sure problem still persist or resolved.
Please try below steps.
1. enter the following line in /etc/inetd.conf file
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd
2. Start inetd daemon using below command
#inetd -c

3. Enter a free ip address in following file.
/etc/opt/ignite/instl_boottab

I am sure your "sea lan install" will work.
Regards
Ran