OFFLINE DIAG

[joe_91]

I was told the primary root disk on our N class (production) does not have offline diagnostics loaded. This tool is useful in the event the system will not boot up after a hardware replacement or system failure.

To load offline diagnostic on root's primary c1t6do

The following command:

mkboot -b /usr/sbin/diag/lif/updatediaglif2 \
-p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c1t6d0

Questions:

1. Is this correct?
2. Are there any issues running this command on the production server?
3. How do i find out if the other systems have the offline diagnostics loaded?
4. Shd the mkboot command be run is single-user mode?

Thanks

Joe.

[Jeff_Traigle]

1. Yes. All disks in a bootable mirrored set need to have this command run on them to install/update the diagnostic files.

2. Not in my experience.

3. lifls (if they are loaded, you'll see more than those 5 files in the -p options... also use -l option on lifls to verify both disks if mirrored so you know you have the same versions of the files on both disks)

4. It can be run in multi-user mode just fine. It's simply writing to the LIF portion of the disk. No impact to users.

[Andrew Rutter]

hi joe,

The command looks fine to me aslong as you have a 64bit install, you probably will have on the N4000

This should not cause any problems while the system is up and running either.

To check if they are installed run this command to check the lif area

#lifls â l /dev/rdsk/cxtxdx

where x = your root disk device

(man lifls for more details)

You can run this in multi user mode but will need root/admin permissions

Andy

[Andrew Rutter]

try again with the lifls command

#lifls -l /dev/rdsk/cxtxdx

Andy

[joe_91]

Thanks.. This what i have from the lifls command on two nclass and lclass servers..

I have attached the text file.

Thanks

Joe.

[joe_91]

This is what i have on the nclass machine:


bs400(N-Class)[/]# lifls -l /dev/rdsk/c1t6d0
volume ISL10 data size 7984 directory size 8 99/10/28 15:23:53
filename type start size implement created
===============================================================
ODE -12960 584 880 0 03/07/11 14:28:27
MAPFILE -12277 1464 128 0 03/07/11 14:28:27
SYSLIB -12280 1592 353 0 03/07/11 14:28:27
CONFIGDATA -12278 1952 249 0 03/07/11 14:28:27
SLMOD2 -12276 2208 141 0 03/07/11 14:28:27
SLDEV2 -12276 2352 152 0 03/07/11 14:28:27
SLDRV2 -12276 2504 626 0 03/07/11 14:28:27
SLSCSI2 -12276 3136 120 0 03/07/11 14:28:27
MAPPER2 -12279 3256 145 0 03/07/11 14:28:27
IOTEST2 -12279 3408 954 0 03/07/11 14:28:27
PERFVER2 -12279 4368 126 0 03/07/11 14:28:27
PVCU -12801 4496 64 0 03/07/11 14:28:27
SSINFO -12286 4560 2 0 03/07/11 14:28:27
ISL -12800 4568 240 0 99/10/28 15:23:53
AUTO -12289 4808 1 0 99/10/28 15:23:53
HPUX -12928 4816 800 0 99/10/28 15:23:53
LABEL BIN 5616 8 0 05/01/20 13:19:30

If offline diagnostic is not loaded then how would i know? what command would tell me that and what to look for?

Thanks

Joe

[Andrew Rutter · Accepted solution]

joe,

with what you have posted you do have the diagnostics on that disk

that command shows what is installed in the lif area.

From the top line down

ODE > SSINFO are parts of the diagnostics.
ODE = offline diagnostics environment

If you did not have them then the output would just have these plus a PAD file

ISL -12800 4568 240 0 99/10/28 15:23:53
AUTO -12289 4808 1 0 99/10/28 15:23:53
HPUX -12928 4816 800 0 99/10/28 15:23:53
LABEL BIN 5616 8 0 05/01/20 13:19:30

The -p part in the mkboot command preserves these parts already in the lif.

Also you can tell you have the 64bit version here aswell by looking at the output of IOTEST2 and MAPPER2.

If it was 32bit then they would just be MAPPER an IOTEST without the 2.

sorry I didnt get back to you sooner, and thanks for the points, hope this bit makes sense to you aswell.

Andy

[joe_91]

thanks a ton

joe