Ignite Lan booting

[Gordon_3]

Hi all,

I have setup an ignite server and client and boot helper system. client and helper are on the same subnet, and server is on another subnet. Somehow I get the error.

Initializing boot Device.


Boot IO Dependent Code (IODC) Revision 2


IODC ENTRY_INIT failed. Error Status: -4

The IODC for this boot device was unable to provide text describing the failure.
IODC ENTRY_INIT[Return Messages] failed. Error Status: -2

0x0000 0000000000000000 0000000000000000 0000000000000010 0000000083fdddb0
0x0004 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0008 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x000c 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0010 0000000000000005 0000000000000000 0000000000000000 0000000000000000
0x0014 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0018 0000000000000007 0000000000000000 0000000000000000 00000000f3ffa029
0x001c 00000000f0660006 0000000002202022 0000000000007580 0000000088880001


Any idea on what this error indicate? Also I have a little query about the "temp" ip address assignment in the /etc/opt/ignite/instl_boottab, suppose I require this IP in both my helper & server? If yes, is it require the same? Finally, for the IP, I should assign a IP belongs to ignite server segment or helper segment? Thx.

Gordon

[Ravi_8 · Accepted solution]

Hi Gordon

when the ignite server and client are on different subnet, servr and helper must be on same subnet.

[Gordon_3]

hi Ravl,

Thx for your info. But I do try to setup the helper in the same segment with client, and it work ( it's in testing machines, above is in production env. and not working... ) So can u pls double confirm? Thx.

Gordon

[unixdaddy]

init -4 usually means disk is duff. Check the disk for errors.

[Gordon_3]

Hi Duff,

Thx, but u mean the server disk, I guess, right? If not error found, will it be file issue? Any command to verify the ignite image is OK?

Gordon

[Ollie R]

Hi Gordon,

Can you confirm that your client and boot helper are connected via the core lan of your client?

Also, how many LAN cards does the boot helper have?

Have you configured the boot helper correctly?
Are there any messages in the syslog of your boot helper? Has a timestamp been put the client entry in the file /etc/opt/ignite/instl_boottab?

As for the temp address, you don't understand exactly what you mean with "suppose I require this IP in both my helper & server". Please clarify.

Finally, yes, the chosen temporary IP must be in the same network segment as the boot helper.

Cheers,

Ollie.

[Ravi_8]

Hi Gordon

client and helper can't be in same subnet for the ignite to work. while booting the client, the server has to put kernel image on the helper and status of the client will be directed to server via helper. This happens only when server and client are on same subnet.

for your second question, you have to assign the IP belonging to server segment

[Ollie R]

Hi Gordon and Ravi,

The client (the system being installed) must be on the same segment as the boot helper - that is why the boot helper is needed in the first place!!!

Ollie.

[Gordon_3]

Hi Ollie,

Our env is a little bit complicated. Ignite server is L-class, and using the Core I/O Lan, it using segment A. Those clients are N-class which has 2 Lan card, primary is connecting path 0/0/0/0, 10/100 Lan port ( I suppose it's also core lan, right?? ), second is connect to PCI 100BT lan card. 2 Lans on N-class are on different segment, say segment B & C ( not sure it do have impact to Ignit ? ) For Boot helper, as it's also N-class, so again, 2 Lan also with 2 same different lan segment, so segment B & C. Frpr Ravi reply above, seems I have setup wrongly for Helper as helper need to be on segment A, right?

For syslog, believe I need to test again to make sure if it get message or not.

For temp address, sorry for the confuse, I mean should I assign those temp Booting IP address for client to boot in BOTH ignite server & helper? If yes, should they be the same? I am very confusing on this.

Many thx again.

Gordon

[Ollie R]

Hi Gordon,

The following points must be correct:

* the client core lan (yes, 0/0/.....) must be physically connected to the same segment as the boot helper

* the "temporary" IP address must be in the same segment as the boot helper LAN card to which it is attached - this should be a unique IP address that nothing else is using OR is going to use!

* the file /etc/opt/ignite/instl_boottab must contain a line specifying the temporary IP address - if there is a timestamp or MAC address on this line REMOVE IT otherwise it will be reserved for the MAC address specified and may also be subject to a timeout!

This should at least get the install going.

Let me know how it goes,

Ollie.

[Gordon_3]

Hi Olle,

Follow yr suggestion, and now it still fail but get a different error result code. Screen like:

Booting....
Failed to initialize.

ENTRY_INIT
Status = -7

Any idea?

Gordon

[Ollie R]

Hi Gordon,

Sorry for the late response - I've not been getting any update e-mails today from ITRC!

Can you check your syslog for errors and the instl_boottab for changes?

Ollie.

[Gordon_3]

Hi Olle,

In the helper syslog, I found below sentence.

Sep 6 18:25:02 corph ftpd[20085]: FTP session closed
Sep 6 18:25:26 corph instl_bootd[22340]: instl_bootd: No suitable IP address
found in: /etc/opt/ignite/instl_boottab

However, I sure I have add one ( just one ) entry which is an IP for helper LAN segmenet and its no use..

For server, no special log observer...thx.

Gordon

[Ollie R]

Hi Gordon,

OK, looks like the systems are communicating at least! I think we're nearly there!

What does your instl_boottab look like? Can you attach a copy?

What IP addresses belong to your boot helper? Again, can you give details?

Ollie.

[Gordon_3]

Hi Olle,

My instl_boottab entry is like this.

# Example: (lines are intentionally commented out)
# 15.1.54.125 # IP address usable by any client
# 15.1.54.126:080009123456:19960116132331 # Entry usable by all (used already)
# 15.1.54.127:::reserve # Reserve this entry once used.
# 15.1.54.138:080009123457::reserve # Reserve an IP-Addr for specific host
#
..4.20:::
..4.21:::

My helper IP address is ..4.145.

My ignite server IP is ..1.1

Would this help?

Besides, I found another information, when I do the "sea lan install", it do indicate another testing ignite server IP. For this testing ignite server, it's in ..4 segment, so it can lookup without the helper...

Any comment, thx.

Gordon

[Gordon_3]

Hi Olle,

I have a very very good news. I finally figure out what happen now !!!!!

I think it's quite good to share to all who also encounter the -7 error when try to boot ignite server.

My problem lies on this.

1. instl_bootd will be hang when somehow something set wrongly and cause ignite client not able to boot, u should kill this process whenever u try to reboot and test again.

2. Big tricky thing happen. the "temp IP" assign in /etc/opt/ignite/instl_boottab need carefully design, my problem lies on my helper IP is ..4.145 and my netmask is 255.255.255.128, so my first time assign temp IP ..4.123 actually is a different LAN segment to helper and this cause fail !!!
After I change it to ..4.146, it work fine!!!! Cool... hope my stupid mistake can help those ignite user ^_^ Thx again all for yr help..

Gordon

[Gordon_3]

Hi Olle and all,

My stupid story has 2nd part....too bad...

at this stage, I am able to boot lan from ignite helper, and can "start" the restore, however, somehow it got stuck at one step... then timeout by the ignite server. I found below sentence in ignite server.

Sep 10 00:01:33 hkgbkup3 tftpd[695]: sendfile: recv: Can't assign requested addr
ess
Sep 10 00:01:41 hkgbkup3 tftpd[713]: sendfile: recv: Can't assign requested addr
ess
Sep 10 00:01:42 hkgbkup3 tftpd[714]: sendfile: recv: Can't assign requested addr
ess
Sep 10 00:01:48 hkgbkup3 tftpd[719]: sendfile: recv: Can't assign requested addr
ess
Sep 10 00:01:52 hkgbkup3 tftpd[720]: sendfile: recv: Can't assign requested addr
ess


For helper, not much log can be seen. Any idea on above sentence mean? I have tried to add same temp IP as helper into server instl_boottab...

Thx. again

Gordon

[Ollie R]

Hi Gordon,

At least we're getting somewhere! 8O)

The only time I've seen this problem before is when you try to assign an "illegal" subnet mask - "your all zero subnet violates RFC1122".

(There's also the possibility that you need patch PHNE_19936 [latest PHNE_22507] if you're running 10.20).

Please check your netmask!

Ollie.

[Gordon_3]

HI Olle,

Sorry that I don't have much knowledge on RFC standard, all my servers including ..1 & 4 segment are using subnet masks 255.255.255.128, so u mean there is something wrong in my setting? The subnet mask is given by our network team collegues.
Pls enlighten, thx.

Bgds,
Gorodn

[Elli Wang]

Gordon:
Don't need to worry about the tftpd sendfile error. Since your ignite server can resolve the name of your client. Since your subnet is 25 bits, the NIC can not bind to it's IP address if you don't turn of the subnet check. Howevr, the tricky part is during the ignite you can not use ndd to change. Which stage does your clinet fail after booting?

Elli

[Elli Wang]

Gordon:
My brain and fingers don't work together. I meant if your ignite server can not resolve the the name of the clinet, it will put these error in the syslog.

Elli

[Gordon_3]

HI Elli,

Thx. but since the Ignite server is also the DNS server, so it can resolve the hostname of the client. Also


x ./dev/mem, 0 bytes, 0 blocks, character device
x ./dev/rroot, 0 bytes, 0 blocks, character device
x ./dev/root, 0 bytes, 0 blocks, character device
x ./dev/tty, 0 bytes, 0 blocks, character device
x ./dev/syscon, 0 bytes, 0 blocks, character device
x ./dev/systty, 0 bytes, 0 blocks, character device
x ./tmp/set_locale, 3115 bytes, 7 tape blocks
x ./var/adm/sw/security/_ACL, 40 bytes, 1 tape blocks
x ./var/adm/sw/security/_OWNER, 62 bytes, 1 tape blocks
x ./var/adm/sw/security/_PROD_DFLT_ACL, 55 bytes, 1 tape blocks
x ./var/adm/sw/security/_SOC_DFLT_ACL, 55 bytes, 1 tape blocks
x ./var/adm/sw/security/secrets, 15 bytes, 1 tape blocks
x ./var/adm/sw/defaults, 1252 bytes, 3 tape blocks
x ./var/opt/ignite/local/manifest/template.def, 14243 bytes, 28 tape blocks
x ./opt/ignite/bin/print_manifest, 40960 bytes, 80 tape blocks
x ./opt/ignite/share/man/man1m.Z/print_manifest.1m, 1873 bytes, 4 tape blocks
x ./configure3, 434176 bytes, 848 tape blocks
x ./monitor_bpr, 20480 bytes, 40 tape blocks


* Download_mini-system: Complete



* Loading_software: Begin

* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (Ignite recovery at Mon Sep 9 15:00:39
EAT 2002).
* Mon Sep 09 18:21:55 EDT 2002: Starting archive load of the source
(Ignite recovery at Mon Sep 9 15:00:39 EAT 2002).
* Processed 10% of archive
* Processed 20% of archive
* Processed 30% of archive
* Processed 40% of archive
* Processed 50% of archive
* Processed 60% of archive
* Processed 70% of archive
* Processed 80% of archive
* Processed 90% of archive
* Completed 100% of archive
* Mon Sep 09 18:29:34 EDT 2002: Completed archive load of the source
(Ignite recovery at Mon Sep 9 15:00:39 EAT 2002).
* Executing user specified script:
"/opt/ignite/data/scripts/os_arch_post_l".
* Running in recovery mode (os_arch_post_l).



The client will hangup here, it wait forever and I observe that there is no activity in the machine ( Coz the LED of Root disks indicate there is no activity... ) Any hint?

Gordon

[Ollie R]

Hi Gordon,

So it seems the Ignite archive completes successfully but the post-archive script is hanging.

If you have a look at the file
"/opt/ignite/data/scripts/os_arch_post_l"
on your ignite server is there anything unusual in there apart from the usual "save_file" and "rm" commands? Anything that might cause a hanging situation?

It might be worth putting some debugging comments in this script (though copy it first!)to see exactly where the problem lies - maybe try putting "set -x" at the top of the file (though under the "#!/usr/bin/ksh" obviously!). Then we can see which command is causing the hang (or maybe we'll see the script completes and the problem is after this point......).

Good luck,

Ollie.

[Gordon_3]

Hi Ollie,

Thx, it's a great point for me to look at, I will try your solution to see what happen on the script.. will give you some idea after that.

Gordon

[Gordon_3]

# The ioconfig files are handled by hw_instance_num config file
# keyword, however IUX can only preserve instance numbers for
# drivers that are in the INSTALL kernel. If this is a problem,
# then you can uncomment the next two lines. However doing this
# can cause some problems when cloning to different hardware.

# save_file /etc/ioconfig
# save_file /stand/ioconfig

# save_file /etc/eisa/config.log
# save_file /etc/eisa/config.err

echo "Start part for ioconfig part"

save_file /etc/eisa/system.sci
merge_file /var/adm/sw/security/_ACL
merge_file /var/adm/sw/security/_OWNER
merge_file /var/adm/sw/security/_PROD_DFLT_ACL
merge_file /var/adm/sw/security/_SOC_DFLT_ACL
save_file /var/adm/sw/security/secrets
save_file /var/adm/sw/defaults
save_file /var/adm/sw/security/secrets
save_file /var/adm/sw/defaults
save_file /var/opt/ignite/local/manifest/manifest
save_file /var/opt/ignite/local/manifest/manifest.info
save_file /var/opt/ignite/local/manifest/manifest.oinfo
save_file /var/opt/ignite/local/manifest/manifest.orig
save_file /var/opt/ignite/local/manifest/manifest.seed
save_file /var/opt/ignite/local/manifest/template.def
save_file /opt/ignite/bin/print_manifest
save_file /opt/ignite/share/man/man1m.Z/print_manifest.1m
save_file /etc/kbdlang
save_file /etc/nsswitch.conf
rm -f /stand/bootconf
rm -f /etc/dhcpclient.data
#rm -rf /var/adm/crash/*
# remove_tlinks
# save_file /opt/upgrade/bin/tlinstall
# rm -f /opt/upgrade/bin/tlinstall
return 0
fi

I will try to find out why it stuck on above sub-function.. thx.

Gordon