Not able to query mstm in my ia server

[Ah Young]

Hi guys,

I was not able to query the following. Is there any step for me to activate?

mstm -> information ->run
even cstm command is not able to output any information.

[Mridul Shrivastava]

Could you please try executing the following command:

echo "map selall info;wait infolog" | cstm > /tmp/cstm.txt

check the cstm.txt and if there is any error please post the error message.

[RAC_1]

Try re-starting diagnostics.

/sbin/init.d/diagnostics stop
/sbin/init.d/diagnostics start

[Darrel Louis]

Hi,

Can try the following:

# cstm
cstm > map all
cstm > sel dev 1;info
cstm > infolog

Do you get any information back?

Also read the following Vulnerability:
http://www4.itrc.hp.com/service/cki/docDisplay.do?admit=-938907319+1151051258686+28353475&docId=c00657001

Darrel

[Ah Young]

Hi Rac,

Restarted diagnostics, but still having the same problem in query mstm -> information ->run

Hi Mridul,

able to run echo "map selall info;wait infolog" | cstm > /tmp/cstm.txt and there is no error in the out put

Hi Darrel,

also able to run the below.

# cstm
cstm > map all
cstm > sel dev 1;info
cstm > infolog

[Mridul Shrivastava · Accepted solution]

Use these steps to diagnose the problem:

1. Type cstm to get into the command line user interface.

2. Type uial to view the user interface activity Log.

This log should indicate the problem with xstm or mstm and how to fix it.

[Mridul Shrivastava]

I would also suggest you to check the Support Plus Bundle for online diagnostics. When it was updated last??

[Ah Young]

Hi Mridul,

Thanks. after typing the uial, there is a lot of error. I will log a call to hp support team.

[Andrew Merritt_2]

In your steps, you don't select a component to run the info tool on, so nothing will happen.

If it works when you select everything, as your reply suggests, the answer is that you need to do:

mstm -> select device -> information -> run

You are missing the second step. By default, none of the devices is selected.

One difference from PA, there is no separate info tool for CPU anymore, that is covered by the System info tool, so in that case you need to select 'system' instead of 'cpu'.

Andrew

[Ah Young]

sorry for that I missed out on the device. Indeed I did choose device, but no output.

[Andrew Merritt_2]

Ok, which device did you choose? I'm guessing you are selecting one that doesn't actually have an info tool, since you're not getting a problem when you select all the devices, or selecting device 1.

You can see the tools available for a device, once having selected it, by running the 'cds' command in cstm.

Can you give an example of the errors you refer to in the 'uial' output?

Andrew

[Ah Young]

Hi Andrew,
Thanks =D

I chose CPU. Below is some of the error. I choose 4 most lastest one.

Mon Sep 12 11:35:27 2005: User Name: root, UI Process ID: 15894

The core user interface failed to retrieve input from
the target user interface (the program which
interfaces directly with the user.)

Mon Sep 12 11:35:27 2005: User Name: root, UI Process ID: 15894

The User Interface exited with status (14) due to an
unexpected error.

Possible Causes/Recommended Action:

Internal Application error.

Fri Sep 30 16:21:47 2005: User Name: root, UI Process ID: 1687

The User Interface exited with status (193)
indicating receipt of an unexpected signal (1).

Possible Causes/Recommended Action:

Internal Application error.

Mon Jun 26 23:48:36 2006: User Name: root, UI Process ID: 3310

The User Interface exited with status (193)
indicating receipt of an unexpected signal (1).

Possible Causes/Recommended Action:

Internal Application error.

[Mridul Shrivastava]

Did you get the same result if you select device as disk or memory etc....

Did you get all the errors rectified which were showing earlier and told that you will log a call with HP. whats the outcome of that...

[Andrew Merritt_2]

Ok, choosing CPU explains what you are seeing, see my earlier post where I mentioned that STM no longer has any CPU-specific tools on IA systems. To see the details of CPUs, select 'system' and then run the information tool.

Not sure if the uial errors are connected with that or something else. I'll see if I can check this.

Andrew

[Andrew Merritt_2]

I don't think the uial errors are connected with your question, especially given the dates of them. I think the most recent two are due to someone killing the stm process with SIGHUP (could be automatically at logout, for example). It's not worth thinking about the older ones anyway, you should have installed a new version of the OnlineDiags since then anyway ;-)

Andrew

[Ah Young]

Hi Andrew,

Thanks. I am able to query system.

Hi Mridul,

I am busy today with some server issue, hence no chance to log call with them.

[Ah Young]

actually the reason why i am query mstm --> cpu ---> information ->run, is to see the PDC version on my server. I am able to see it in Pa rics server, but i am not able to see it in IA. Do you all have any idea??



Product ID: CPU Module Type: 0
Hardware Model: 0x5c4 Software Model: 0x4
Hardware Revision: 0 Software Revision: 0
Hardware ID: 0 Software ID: 139901517
Boot ID: 0x2 Software Option: 0x91
Processor Number: 0 Path: 160
Hard Physical Address: 0xfffffffffffa0000 Soft Physical Address: 0

Slot Number: 8 Software Capability: 0x100000f0
PDC Firmware Revision: 44.28 IODC Revision: 0
Instruction Cache [Kbyte]: 512
Monarch: Yes Processor State: Active
Data Cache [Kbyte]: 1024
Instruction TLB [entry]: 160 Processor Chip Revisions: 3.0
Data TLB Size [entry]: 160
Serial Number: 0


----------------- Processor 0 HPMC Information - PDC Version: 44.28 ------

[Andrew Merritt_2]

Does /usr/contrib/bin/machinfo give you what you need? That should show the firmware level (you won't see PDC as that is not a term used on IPF systems).

Does the system Info tool work otherwise, apart from not giving the FW levels?

Andrew

[Ah Young]

i do know about machinfo. But i was not able to find PDC version, hence my idea was, it can not be use~~

How can I access system Info tool ??

[Andrew Merritt_2]

I thought it was the Firmware level you wanted, there is a section in the machinfo output which shows this, e.g.:

Firmware info:
Firmware revision = 01.13
FP SWA driver revision: 1.18
IPMI is supported on this system.
BMC version: v02.20

The FW level info is also at the top of the STM 'system' information tool output:

Product ID : ia64 hp server rx4640
Product Number : A6961A
System Firmware Revision : 01.13
BMC Revision : v02.20
System Serial Number: : DEH44100CL



PDC (Processor Dependent Code) is a term which applies only to PA systems, so there is no PDC on an IA system, you'll see references to System Firmware instead. The role of the PDC is largely performed by the IPMI on IA systems.

As far as the system info tool goes, I think you've already done this:
mstm --> system ---> information ->run

Andrew

[Ah Young]

oh... thanks for the info.
so in pa rics, we update pdc, then in IA, what do we usually update?

[Andrew Merritt_2]

System Firware