1834696 Members
2182 Online
110069 Solutions
New Discussion

memory

 
SOLVED
Go to solution
Mark Mitchell
Trusted Contributor

memory

Is there a way from the system side to find out the current memory config. I would like to avoid having to open the server up if it can be helped. Just looking for the number of slots and chips ect...
8 REPLIES 8
A. Clay Stephenson
Acclaimed Contributor

Re: memory

If you have stm if works very well.
If it ain't broke, I can fix that.
melvyn burnard
Honored Contributor

Re: memory

go click on the SEARCH button at teh top left side of the ITRC forums page
choose per-to-peer forums
enter the words: memory physical
and then start the search and see how many documents are retrieved.
One of these should help you.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
James R. Ferguson
Acclaimed Contributor
Solution

Re: memory

Hi Mark:

You can assess the physical memory chips installed by using the Support Tools Manager (STM):

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

From this output, you will be able to see the chips and the chip sizes installed.

...JRF...
Vincenzo Restuccia
Honored Contributor

Re: memory

Try any of the following.

1. #dmesg |grep -i phy (may not work if the message buffer is filled up with some other messages)

2. # echo "mem_ptr/D"| adb /stand/vmunix
/dev/mem (gives in number of bytes)
3. SAM --> Performance Monitors --> System Properties ---> Memory
Mark Mitchell
Trusted Contributor

Re: memory

The stm seems to be the thing here, but I am having trouble starting the diagmond
James R. Ferguson
Acclaimed Contributor

Re: memory

Hi Mark:

Try stopping & restarting 'diagmond' with:

# /sbin/init.d/diagnostic stop
# /sbin/init.d/diagnostic start

...JRF...

Mark Mitchell
Trusted Contributor

Re: memory

That will restart it but first I had to edit
/etc/rc.config.d/diagnostic so that it has a value of 1. Its a 1 line file.
James R. Ferguson
Acclaimed Contributor

Re: memory

Hi Mark:

Yes, that's true, and a common, standard feature of the /sbin/init.d/ startup paradigm. Sounds like your in business!

...JRF...