Procedure for stm from command line to collect system information

[Zubair_2]

Hi,

I require your help...for resolving the following issue.

Oct 17 08:19:20 alps vmunix: DIAGNOSTIC SYSTEM WARNING:
Oct 17 08:19:20 alps vmunix: The diagnostic logging facility is no longer receiving excessive
Oct 17 08:19:20 alps vmunix: errors from the I/O subsystem. 10 I/O error entries were lost.

Model : n4000
OS: hpux - 11.0


2) Procedure for running stm from command line.

[Stuart Abramson]

I normally figure this out from syslog and dmesg.

I have used "cstm". Here is an old example. I remember it being complicated and difficult. There was also a graphical version. There is a help.

/usr/sbin/cstm

cstm> map

cstm> select device DEV_NUM_OF_CPU

Dev Last Last Op
Num Path Product Active Tool Status
=== ==================== ========================= =========== =============
1 system system ()
2 0 Bus Adapter (582)
3 0/0 PCI Bus Adapter (782)
4 0/0/0/0 Core PCI 100BT Interface
5 0/0/1/0 PCI SCSI Interface (10000

29 8 MEMORY (95) Information Successful
* 30 160 CPU (5c5) Information Successful
31 166 CPU (5c5) Information Successful



cstm> info

cstm> infolog

The cstm is the Character-based Support Tools Manager. The map command lists the
hardware on the box; the info command starts the Information Log; the infolog
commands display the contents of the Information Log. Here's my output:


-- Converting a (5060) byte raw log file to text. --
Preparing the Information Tool Log for CPU on path 160 File ...

-- Information Tool Log for CPU on path 160 --

Log creation time: Mon Jul 10 15:29:39 2000

Hardware path: 160


Product ID: CPU Module Type: 0
Hardware Model: 0x5c5 Software Model: 0x4
Hardware Revision: 0 Software Revision: 0
Hardware ID: 0 Software ID: 116901567
Boot ID: 0x2 Software Option: 0x91
Hard Physical Address: 0xfffa0000 Soft Physical Address: 0
Slot Number: 8 Software Capability: 0x100000f0


PDC Firmware Revision: 40.19 IODC Revision: 0


Instruction Cache [Kbyte]: 512 Processor Speed: N/A
Data Cache [Kbyte]: 1024 Processor State: N/A
Instruction TLB [entry]: 160 Processor Chip Revisions: 2.3
Data TLB Size [entry]: 160 2nd Level Cache Size:[KB] N/A
Serial Number: 0

Hope it helps.

[Torsten.]

Errors came to rapidly, but usually it's always the same error.

Have a closer look to the syslog file, there is much more information. Errors are logged by EMS too, so have a look in roots mailbox.

[Ermin Borovac]

The following should show you what's logging I/O errors.

# /usr/sbin/cstm
> runutil logtool
> fr
> fl

[Andrew Merritt_2]

In syslog.log you should also see an earlier message saying that the diagnostic logging facility was receiving too many errors from the I/O subsystem, and was suspending logging. This might even be a few days before, since the resuming message is put out the next time a message is successfully logged. If there was a burst of errors, causing the suspension of logging, and then no more for a day or two, the resumption message would then be logged.

The errors are processed by diaglogd, and it reads from a buffer; if the buffer gets full because errors are being logged faster than diaglogd can deal with them, then you get this situation.

If you run 'logtool' in STM, you should see some I/O errors recorded around the time that the logging was suspended. You won't necessarily see any events from the EMS HW monitor, it would depend on the severity of the error, but you might see some in /var/opt/resmon/log/event.log.

Regarding the second question, STM has 3 interfaces, xstm, mstm and cstm. cstm is probably the one you want, as it's command driven, and you can pipe the commands you want into it, which I think is what you're asking for (if that's not what you want, can you explain further what you're trying to do?).


For example:
echo "selclass qualifier memory;info;wait;infolog" | cstm

(all on one line) will select memory, run the info tool and display the output.

Andrew

[Stuart Abramson]

Zubair,

Publish points...

Close thread..

Stuart

[Robert-Jan Goossens]

Hi,

Try this command.

# echo "selclass qualifier system;info;wait;infolog" | /usr/sbin/cstm > /tmp/cstm_log

# cat /tmp/cstm_log

Regards,
RJ

Please close this thread and assign points !