[Q] tftp network trouble during igniting

[Tony, Lim]

All ..

I am trying to configure the igniteUX to deploy HPUX client.

But, there was some troubles that I don't know what cause is.

Once It is ignited, it takes more 10 hours to load a gold image from server.

More curious thing is, it did not used to be at past.

I mean, I used to ignite some clients with this ignite server that have same configuration.

Please, refer below information & let me know what do I do to solve this trouble.

Thanks in advance.



1. /var/adm/syslog/syslog.log
===================================
Aug 8 11:05:31 igniteux tftpd[7662]: sendfile: recv: Can't assign requested address
Aug 8 11:05:31 igniteux tftpd[7676]: sendfile: recv: Can't assign requested address
Aug 8 11:05:37 igniteux tftpd[7681]: sendfile: recv: Can't assign requested address
Aug 8 11:05:44 igniteux tftpd[7689]: sendfile: recv: Can't assign requested address
Aug 8 11:05:46 igniteux tftpd[7690]: sendfile: recv: Can't assign requested address
Aug 8 11:06:23 igniteux tftpd[7709]: sendfile: recv: Can't assign requested address
Aug 8 11:06:25 igniteux tftpd[7710]: sendfile: recv: Can't assign requested address
Aug 8 11:16:21 igniteux tftpd[7655]: Timeout (no requests in 10 minutes)


2. root-igniteux:/var/adm/syslog# instl_adm -d
====================================
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="152.149.163.58"
netmask[]="255.255.255.224"
route_gateway[0]="152.149.163.33"
route_destination[0]="default"
# end instl_adm defaults.
#_hp_lanadmin_args="-X 100HD"

3. /var/opt/ignite/data/Rel_B.11.11/11.11_client_os_5.5
==================================
nfs_source = "152.149.163.58:/var/opt/ignite/archives/11.11/PS5.5"


4. /var/opt/ignite/INDEX
===============================
cfg "11.11 Client PS 5.5" {
description "HP Build for 11.11 Clients PS 5.5"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/opt/ignite/data/Rel_B.11.11/11.11_client_os_5.5"
"/var/opt/ignite/saved_cfgs/11.11_client_da_5.5"
"/var/opt/ignite/saved_cfgs/11.11_client_kp_5.5"
"/opt/ignite/data/Rel_B.11.11/hw_patches_cfg"
}

[Florian Heigl (new acc)]

"Once It is ignited, it takes more 10 hours to load a gold image from server.

More curious thing is, it did not used to be at past."

This smells like a duplex issue...

[Steven E. Protter]

Shalom,

Few ideas come to mind.

1) instl_adm can be used to switch the Ignite file transfer to a faster NIC card after initial boot, which must be on a built in NIC.

2) Its possible you built files bigger than 2GB into the Ignite image but pax_iux can't unpack them. This is a version specific issue, and you will need to check the logs on the system that is building slowly. The install logs on the client are critical to determining the problem.

SEP

[Tony, Lim]

Thanks replyers ..

But, I guess that it is not duplex issue.

Refer belows
-------------------
root-igniteux:/root# lanadmin -x 0
Current Config = 100 Full-Duplex MANUAL

And.. my gold image is not over 2GB, actually I just overed 1 GB.

All ip address of above things are correct. I have no idea what cause this network lagging.

[Florian Heigl (new acc)]

That's the igniteservers duplex setting. now You only need to check the one on the client and well... look at Your post:

2. root-igniteux:/var/adm/syslog# instl_adm -d
====================================
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="152.149.163.58"
netmask[]="255.255.255.224"
route_gateway[0]="152.149.163.33"
route_destination[0]="default"
# end instl_adm defaults.
#_hp_lanadmin_args="-X 100HD"

I hope and You should verify that the card is at 100FD *and* Your switches are set the same way, not to autoneg.

Sorry I keep pushing You that route, but it's just been 5 weeks since a lost instl_adm duplex setting ruined my whole weekend. (at last it wasn't me that lost it =)

[IT_2007]

Tony,

I had same problem and found the issue was with Ignite server setting was 100HD. Make sure that your switch port set to 100 Full Duplex, No auto negotiation. While loading image, is it showing that NIC card being activated with 100FD?

[Tony, Lim]

All.. thanks for your advice.

As a result, I found what cause this network troubles.

It caused by difference of duplex between ignite server and switching hub.

My ignite server was set as 100 full-duplex fixed, but switch was set as auto-nego.

So, there was some network troubles due to that.

After I changed igniteUX value to auto, It was fixed and normally igniting was possible.

Now, It taks only 30-40 min to ignite per 1 client.

Thanks all.