make_net_recovery error

[MikeL_4]

I received the following error from a make_net_recovery run last night:

ERROR: System error,
/opt/ignite/bin/instl_adm failed checking
/var/opt/ignite/recovery/client_mnt/
0x00306E4B2612/recovery/2004-11-18,04:00/
system_cfg

Just started receiving this message after this make recovery had been running for a few weeks. Not sure what is causing it ??

[G. Vrijhoeven]

Hi Mike,

Can you do a path/rights check on /var/opt/ignite/recovery/client_mnt/
0x00306E4B2612/recovery/2004-11-18,04:00/
system_cfg

HTH,

Gideon

[Steven E. Protter]

instl_adm is a utility that is used to display and change networking.

There my be a inconsistency in the networking or the connection to the NFS share you are writing your recovery too.

results of:

instl_adm -D
Shold be interesting and compared to this:
lanadmin -x 0

replace the zero with the actual lan number (re lan1 is 1, etc).

SEP

[MikeL_4]

root@vspftp1:[/osg1/log]:=>ite/recovery/client_mnt/0x00306E4B2612 # instl_adm defaults:# NOTE: Manual additions between the lines containing "instl_adm defaults"# and "end instl_adm defaults" will not be preserved.server="192.168.228.105"netmask[]="255.255.255.224"route_gateway[0]="155.90.17.97"route_destination[0]="default"# end instl_adm defaults.root@vspftp1:[/osg1/log]:=>root@vspftp1:[/osg1/log]:=>lanadmin -x 0 Speed = 100 Full-Duplex.Autonegotiation = Off.root@vspftp1:[/osg1/log]:=>lanadmin -x 1Current Config = 100 Full-Duplex MANUALroot@vspftp1:[/osg1/log]:=>lanadmin -x 1root@vspftp1:[/osg1/log]:=>ifconfig lan0lan0: flags=1843 inet 192.168.228.105 netmask ffffffe0 broadcast 192.168.228.127root@vspftp1:[/osg1/log]:=>

[MikeL_4]

Here is the entire recovery.log in case it might help, there are additional messages in it..

[Ermin Borovac]

Please examine output of 'ioscan -f' and check for any disks that might have failed. Also check the output of 'vxprint -g rootdg'

[Sanjay_6]

Hi Mike,

Maybe this link from itrc would help,

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000075563772

The itrc doc id is KBRC00015246.

Hope this helps.

regds

[Sanjay_6]

Hi Mike,

If you are using an older verion of Ignite, this could be another reason why you might be having the problem,

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000071552282

The itrc doc id is UIUXKBRC00011394.

Hope this helps.

Regds

[MikeL_4]

vxprint -g rootdg gives:
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg rootdg rootdg - - - - - -

dm rootdisk01 c2t1d0 - 71678412 - - - -
dm rootdisk02 c2t0d0 - 71678412 - - - -

and I see no other errors, these are also the only two disk on the server.

save_config run gives the attached info with running as: sh -x save_config

[MikeL_4]

One other thing I just noticed is that we have two disk on the server, both in rootdg controlled by Veritas. One of the disk being a mirror of the primary.

What I've noticed is that disk c2t0d0 which is the primary disk is 100% allocated. No where near being fully used within the file systems, but the disk is completely allocated.

Thanks