trying to simulate system recovery for a system w/o a tape drive.

[Charles Holland]

Have been using make_tape_recovery and not had any problems. In the future we are planning on going to a rp7410 w/2 cell boards and then vpar each cell board once to make 4 virtual systems on one physical box. On two of these vpars will not have a tape physically attached to them so I am now trying to understand make_net_recovery.
I have set up my Ignite server on a L2000 and have been successfull in adding a client (an E55) box to the system. In doing so I received one message ""E55" is not on the same subnet with the Ignite-UX server. See the man page for make_boot_tape for information on using the archive you create". This I didn't understand how it could not be on the same subnet but pressed "OK" to trod on. I then proceed to create an archive and everything looked good when the icon turned green. I figured this was a good thing.
Went back to the E55 and rebooted it and interupted the boot to boot off of the lan and recover the system using what the manual calls the "pull" method.
PROBLEM: I can't find the correct combination to boot thru the lan. The closest that I have been able to come is "bo p4 192.0.2.103 install".
When I did SEA from the menu p4 was my designated as my lan.
Interact with IPL (Y or N) n
Booting...
Network Station Address 080009-a715ce
Cannot find ENTRY_TEST.
Failed to initialize
ENTRY_INIT status = -7

Back to the Main Menu. The system physically has a tape drive in it (a DDS1) but I'm trying to simulate having to reinstall the system on one of the vpars that doesn't have a tape. I haven't tried doing a "boot system" from the ignite server(I already messed the E box up accidently and had to figure out how to reset the autofile to boot vmunix) to do the push method, but how would this simulate a system with a crashed vg00? It appears that the client is supposed to already have an OS on it and if it is running, why recover!

[Charles Holland]

Forgot to mention the OS is 11.0 and Ignite is 4.x Sorry

[Steven E. Protter]

make_net_recovery

works just like make_tape_recovery just doesn't require a tape drive.

Its part of Ignite. There is some setup overhead, but you can boot off an Ignite server pretty easily.

Here are some important rules:

You must boot off the built in LAN card, it won't work on non-hp or HP add in LAN cards.

Procedure:

1) Set up Ignite Server

2) Boot HP box

3) Interupt at the 10 second prompt.

4) bo lan.ip_add_of_ignite_server install

SEP

[Tim Adamson_1]

Hi,

Is the E55 on the same subnet as the L2000 Ignite server?

If not, then you will need a boot helper to boot the E55 from the Ignite server.

You can find information in the Ignite-UX Administration Guide available from www.docs.hp.com. Refer to Appendix B.

Cheers!

[Con O'Kelly]

Hi

As Tim has said the client you are trying to boot needs to be on the same subnet as the Ignite Server.
Generally I would try & set up an Ignite Server for each subnet, it makes life alot easier than messing around with boot helpers etc.

SEP has pointed you in the right direction to boot your system from the Ignite Server.
Use the command:
> boot lan install
It should be able to contact the Ignite Server on the that subnet.

A couple of things you need to ensure:
1. Check "bootps" and "instl_boots" service are enabled in /etc/inetd.conf on the Ignite Server. The Ignite install should have done this but its worth checking in case someone has disabled it.

2. You must have allocated some temporary IP addresses (that are not in use), that can be used by Ignite while its booting your client.
You can do this in the Ignite GUI.
Select Options -> Server Configuration -> Confiure Booting IP Addresses.

Have a look at the the makenetrec.txt doco in /opt/ignite/share/doc. It gives you plenty of info on using make_net_recovery.

Cheers
Con

[Charles Holland]

SEP
1)- 3) These were done before 4).
4) Any combination of bo lan install comes back with ERROR: Not a booth path

I can do bo 60/6.0 install and it will ask if I want to interact with IPL, then says Booting and the rest is documented above.

Tim
Everyting I can see on any of our machines indicates that ALL subnets are 255.255.255.0
Boot helper may be an option which may become viable after exhausting all other avenues. If I dont have to pull another machine into the mix I'd rather not.

Con
See above about boot lan install

In the inetd.conf file the instl_boots did not have a # in front of the line but the bootps did. I removed it and then had inetd re-read the conf file.

The temporary ip address was something off the wall like 194.168.15.6 or something like that. We did change it to 192.0.2.250 which is more in our number ranges. Didn't seem to help.

Todays progres.... made some minor changes on the Ignite server, see above. Never was able to get the E55 to boot from the network. Tried to "push" the installation to the client, and that didn't work either. It came up with all kinds of tftp errors on the console. And messages inidcating it could not read the INDEX file. While doing the push proccess many 'tftpd transfer timed out" messages were recorded in the syslog. Wound up booting from my make_tape_recovery tape to get the system back. Using the command 'tftp Ignite-server get /var/opt/ignite/INDEX and was able to retrieve the file from the Ignite-server to the machine we were on.

Maybee it is not possible to boot from a lan on an "E" box.

[Tim Adamson_1]

Hi,

The ENTRY_INIT = -7 means a nonexistent device. So the device address specified may be a valid device address, but it points to a device that is not installed and/or responding.

I had the same problem and required a boot helper but I was definitely on a different subnet.

Also ensure that p4 is the built-in lan.

Check the syslog.log file on the server to see if there are any messages. At least you will know if it is even getting this far in the communication process.

Cheers!

[Con O'Kelly]

Hi Charles

I think you should be able to boot from an E box. If you are on the same subnet then you won't need a boot helper.

A few things to check.

1. The Temporary IP address you are using 192.0.2.250 must be on the same subnet as the client & Ignite server.
So your Ignite server & client must have an IP address of 192.0.2.xxx.

2. Some older systems could not boot using
boot lan.IP install.
Try using:
boot lan.
Where MAC Address is the MAC of the Ignite Server.

3. Also check the /etc/opt/ignite/instl_boottab file on the Ignite server.
The Temporary IP address must be listed in there. If its not, add it manually.

Good idea from Tim to check syslog.log, at least you should be able to see if your client is managing to contact the Ignite Server.

Cheers
Con

[Steven E. Protter]

Thanks for the issues update, I knew this one wasn't so easy.

Most common problems causing the bo lan.ip install to fail:

1) Server is not on the same network and subnet.
2) Lan card speed and duplex is not right. You need to make sure below 1000 BaseT that the switch port and land card are 100 BaseT Manual. This should be done even if lanadmin says everything is okay.

There are some things you can do on the Ignite server side to help with diagnosis.

Before start of processing:

netstat -I 1 3

This takes reading son Interface 1 (lan1) ever three seconds. You should see some bytes hopping through there.

The syntax may be wrong, I think my netstat neeeds a patch or two.

ps -ef | grep boot

before you attempt the boot

same thing after.

If a new process kicks off, then you know something is going on, check the /var/adm/syslog/syslog.log file for errors. If there is nothing, go back to networking.

As I probably said earlier, this will never work through anything but the built in lan. You can boot off that and load off any card you want.

inst_adm -d

This command will let you verify networking after the kernel has been pushed/pulled via the built in lan cards.

SEP

[Steven E. Protter]

Sorry,

netstat -i 1

I know there is a way to set the interval, but my brain is locked right now.

SEP

[Charles Holland]

First for everyone it's FRIDAY! Thank God.
Second review the attachment and it should illistrate that the internal lan's address is 60/6.0, which is what I have been trying to boot through to get to the Ignite server. What the subnets are set to. Last but not least an important excerpt from an HP document.

Tim...Also found document UIUXKBRC00010143 talking about the ENTRY_INIT -7 message.
I don't think that a boot helper could help. See attachment. As far as system messages on the Ignite server there were some "rpcbind: cannot accept connection: bad call sequence number (current state 4)" there were 3 of these. A TON of "tftpd[29561]: Transfer timed out". And a "bootpd[19013]: Exiting after 500 minutes of inactivity". Nothing that I could see regarding the connecting of the client.

Con....I'm not sure but I think item 1 in your response was the answer to item 3. "192.0.2.250:::" is in the
/etc/opt/ignite/instl_boottab file. After reading the document at the end of the attachment I didn't even bother with item 2.

SEP... I think the attachment and the above comments pretty much say it all.

To ALL... Thanks for the efforts in trying to get this going. Now on to other things.