Operating System - HP-UX
1753781 Members
7828 Online
108799 Solutions
New Discussion юеВ

Re: can Ignite version C.7.2 fix the make_net_recovery hang?

 
skt_skt
Honored Contributor

can Ignite version C.7.2 fix the make_net_recovery hang?

Make_net_recovery hangs when it search on SAN disks (NO_HW state)for ISL information.
The Make_net_recovery can be restarted if we do rmsf on the disks with NO_HW state. But the loadfile process still be present even after a kill -9.

Hung process details.

root 19125 1 0 May 7 ? 0:00 /opt/ignite/lbin/loadfile -Tql ISL -f /dev/dsk/c159t0d0
root 26698 1 0 Jun 7 ? 0:00 /opt/ignite/lbin/loadfile -Tql ISL -f /dev/dsk/c159t0d0

Looking for a fix for this bug. Current ignite version is
Ignite-UX C.7.1.93 HP-UX System Installation Services

I checked the release note of Ignite version C.7.2 and found that it says " In response to the request to improve I/O inventory performance,
Ignite-UX has introduced the ability to block particular paths and protocols during inventory. This can be done by using the "inventory_block_path", and "inventory_block_protocols" variables either in the first 8KB in *INSTALLFS or from the hpux boot loader
command line. See instl_adm(4)."

Does any one implemented this?
4 REPLIES 4
Fabian Brise├▒o
Esteemed Contributor

Re: can Ignite version C.7.2 fix the make_net_recovery hang?

Hello santhosh.

check this link out, I think you will find the answer there.


http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1140597
Knowledge is power.
skt_skt
Honored Contributor

Re: can Ignite version C.7.2 fix the make_net_recovery hang?

i have been part of that communication... That is not a practically concluded one.
Steven E. Protter
Exalted Contributor

Re: can Ignite version C.7.2 fix the make_net_recovery hang?

Shalom,

Its not a bug.Ignite is supposed to fail to complete the backup with an erorr message if all disks are not in a good status.

If it just hangs maybe the new version will help.

However if the disk is not in good condition then the baackup will fail because Ignite needs to make sure all configured disks are good before essentially "signing off" that the system is recoverable.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
skt_skt
Honored Contributor

Re: can Ignite version C.7.2 fix the make_net_recovery hang?

We have fixed the root casue of the problem. Removing the NO_HW status device files using rmsf.A script is run which will do this after each device recliam(when ever device access is removed for the hosts).


this is better than giving/specifyin an exclude list with newer ignite version