Command to find out physical memory & hard disk installed

[Ramesh.K.R.]

Hi,

How to find the amount of physical memory & hard disks(size) installed in a tru64 machine ?? are there any commands ??

Thanks & Regards,
Ramesh.K.R.

[Ralf Puchner]

this answer was given in a previous posting.

use "show config" on SRM console or have a look into the binary.errlog. Another approach on V5.x systems is to use the hwmgr command (e.g. hwmgr -show scsi, hwmgr -show comp)

[Michael Schulte zur Sur]

Hi,

run sys_check or use decevent to look at the startup sequence. It will even tell you, what size the memory modules in the slots are.

Michael

[Sreenivasa Prasad V.]

vmstat -P

- Sreenivasa Prasad V.

[Sreenivasa Prasad V.]

uerf -R

- Sreenivasa Prasad V.

[Ralf Puchner]

uerf -R is equal to decevent but can not decode all messages (including fru information) of all machines.

Btw. it is equal to my answer: "look into the binary.errlog" and the answer of michael to use "decevent" ;-)

VMSTAT is a tool to monitor virtual and not physical memory (see "man vmstat").

[Michael Schulte zur Sur]

Hi Ralf,

I knew this would come and I hesitated long whether to write it or not. ;-)
But I came to the conclusion, that although my answer was already covered somewhat by your's, it might still be helpfull to add some more detail.

Michael

[Ralf Puchner]

Michael,

if I tell someone "look into the binary.errlog" then there are two possiblities:

1. he doesn't know the command but can simple use the "apropos" command, ask here in the forum, search within the forum and will get the correct answer.

2. he knows the right command and use it.

otherwise I must write

if ev4 use uerf
if ev45 use uerf
if ev5 use dia
if ev56 use dia
if ev6 use ca
if ev67 use ca

so I will provoke the next question:
"what is ev?", "how can I get the ev information" etc. ;-)

you see giving a specific command not knowing any detailed information about the configuration/hardware leads to follow on questions and a move away from the root problem and the sentence "look into the binary.errlog" is quite clear and a direct pointer.