topic Ignite (network) Recovery problem!! in Operating System - HP-UX

Ignite (network) Recovery problem!!

rveri — Mon, 24 Apr 2006 10:30:37 GMT

Hi All,
Does any one experienced too slow Ignite-UX recovery , on a vpar , from network recovery , from an Ignite ux server.

Server having 2 vpar. vpar2 is down.

From vpar1: executed
# vparboot -p vpar2 -I IP_of_ignite_srv,/opt/ignite/boot/WINSTALL

The Ignite image size is only 3GB , but its 7hours since its going on , only 20% completed.

checked with iostat for that disk , which have the image shows 100(in bps field) i,e 100K/s is tranfering.

Anyone faced such a problem. Or any idea is highly appreciated.

Thanks,

Re: Ignite (network) Recovery problem!!

Sung Oh — Mon, 24 Apr 2006 11:31:00 GMT

Hi,

Mostly, The slow installation process is caused by network. You can check following list of items.

1. resolving IP address and host name.
2. subnet configuration between client and server.
3. version of vpars.

regards,

Sung

Re: Ignite (network) Recovery problem!!

Steven E. Protter — Mon, 24 Apr 2006 11:38:19 GMT

Shalom rveri,

100 Kilobytes a second is not terribly fast. A few probable causes.

network speed is not expected. Sometimes you can use the instl_adm tool to set better speeds, but you need to know from networking what they are supposed to be. Don't guess.

There are log files on the recovered server. You can stop the transfer and go to a shell and look at where it is.

Some older versions of Ignite had trouble unpacking files bigger than 2 GB. I hope that is not an issue now.

SEP

Re: Ignite (network) Recovery problem!!

rveri — Tue, 25 Apr 2006 01:33:17 GMT

Thanks Sung and Steven,

Though its completed after 10hrs ,
HP Suggested to update the Vpar and Ignite-UX products.

Thanks.

Re: Ignite (network) Recovery problem!!

Bob Ingersoll — Tue, 25 Apr 2006 09:42:55 GMT

This can happen if thw switch port the IUX client connects to is not set to autonegotiate mode.

The IUX install kernel defaults to use autonegotiate on the client interface. If the switch port is not also set to autonegotiate you WILL have a duplex mismatch that will severely degrade performance of the LAN connection.