Running STM to check out device status

[Mike Brown_3]

Using the STM character mode, cstm, I've run "info" on all devices - each one has completed successfully except for "Memory".
So when I go to check out the Memory infolog, I get;
"Information Tool Log for MEMORY on path 63 file does not exist"
Any ideas why?
Thanks.

[James R. Ferguson]

Hi Mike:

I always do it this way:

# echo "selclass qualifier memory;info;wait;infolog"|cstm > /tmp/meminfo

...JRF...

[Mike Brown_3]

I'd already run that one since I'd seen you recommend it before in another post.
This what I get;
# cat /tmp/meminfo
Running Command File (/usr/sbin/stm/ui/config/.stmrc).

-- Information --
Support Tools Manager

Version A.20.00

Product Number B4708AA

(C) Copyright Hewlett Packard Co. 1995-1998
All Rights Reserved

Use of this program is subject to the licensing restrictions described
in "Help-->On Version". HP shall not be liable for any damages resulting
from misuse or unauthorized use of this program.

cstm>selclass qualifier memory;info;wait;infolog
-- Updating Map --
Updating Map...
-- Information --
Information Tool Log for MEMORY on path 63 file does not exist.

cstm>

Now, judging by other responses to other posts, it could be the version of STM I'm using, (I know it's not that recent).

[James R. Ferguson]

Hi Mike:

Interesting. I've got A.24.00 on a K560 running 11.0 and A.19.00 on some 10.20 K and D boxes.

Are you running as root? What's the server kind?

...JRF...

[James R. Ferguson]

Hi (again) Mike:

Also, since you indicate that memory is at path 63 (confirm this with an 'ioscan'), does this work (?):

# echo "sel path 63;info;wait;infolog"|cstm > /tmp/meminfo

...JRF...

[Mike Brown_3]

Yes, as root. And it's a D320.
Thanks for the quick responses.

[Mike Brown_3]

James - HW Path is confirmed as 63.
And your last suggestion gives me the same result as above.

[Satish Y]

Try this,

# cstm
cstm> map # list of devices
cstm> sel path 63
cstm> info
cstm> infolog

save above log and view it.

Cheers...
Satish.
Cheers...
Satish.

[Insu Kim]

It looks like that STM has a problem.
If I were in your shoes, I would get the latest version of STM and give it a try again.

[Mike Brown_3]

Ok, guys - I've tried all your suggestions, same result. I suspect my STM install is flaky and needs to be removed and re-done. Just wanted to see if anyone out there suggested anything radically different.
Thanks for your input.