|
|
Ramones
|
|
Oct 13, 2009 10:37:39 GMT
|
|
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
|
|
|
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
|
|
|
Sort Answers By:
Date or Points
|
|
Scot Bean
|
|
Oct 13, 2009 16:07:07 GMT
Unassigned
|
|
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
|
|
Oct 14, 2009 14:17:24 GMT
N/A: Question Author
|
|
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
|
|
Oct 14, 2009 20:40:08 GMT
Unassigned
|
|
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
|
|
Oct 14, 2009 23:56:59 GMT
Unassigned
|
|
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
|
|
Oct 15, 2009 01:28:01 GMT
Unassigned
|
|
You will have to check if bootp and tftp is enable in indetd.conf.
What is the error you got.
BR,
Kapil+ |
|
|
Ramones
|
|
Oct 20, 2009 16:54:40 GMT
N/A: Question Author
|
|
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
|
|
Oct 23, 2009 05:24:14 GMT
Unassigned
|
|
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
|
|
Oct 27, 2009 14:52:47 GMT
N/A: Question Author
|
|
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
|
|
Oct 27, 2009 16:35:13 GMT
N/A: Question Author
|
|
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.
|
|
Oct 27, 2009 16:38:37 GMT
Unassigned
|
|
|
Probably. What server model? |
|
|
Ramones
|
|
Oct 27, 2009 16:40:23 GMT
N/A: Question Author
|
|
Hi
9000/800/rp4440
thanks,
R |
|
|
Torsten.
|
|
Oct 27, 2009 19:29:22 GMT
Unassigned
|
|
|
|
Torsten.
|
|
Oct 27, 2009 19:48:19 GMT
Unassigned
|
|
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
|
|
Oct 28, 2009 11:25:18 GMT
N/A: Question Author
|
|
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.
|
|
Oct 28, 2009 12:24:34 GMT
Unassigned
|
|
Before give up update the firmware!
The firmware is responsible of what the server does during this boot. |
|
|
Ramones
|
|
Nov 4, 2009 16:30:35 GMT
N/A: Question Author
|
|
Hi
I made the firmware update.
The problem persists...I don't have more ideas...
Thanks,
R |
|
|
ranveer
|
|
Nov 15, 2009 15:18:24 GMT
Unassigned
|
|
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 |
|
Printable version
