cstm and ems

[Shah Gaurang B.]

hello experts,

can anybody say me about cstm tool and ems (event monitor system) ? Actualy how to configure and use it i can't understand .

pl. say me.

Thanks to all.

[AwadheshPandey]

cstm is a support tool to know hardware information of system. to use cstm u should have root's priv.
#cstm
cstm>map
cstm>selall
cstm>info
cstm>infolog
pls click for more information
http://docs.hp.com/en/diag/stm/stt_csyn.htm

you can see the information about all the fru's.
ems is event monitoring system.
you can see the logs in
/var/opt/resmon/log/event.log file
pls see the attched doc for more information

http://docs.hp.com/en/diag/ems/emo_all.htm

Awadhesh

[Warren_9]

Hi,

u can use SAM to configure the EMS and it can monitor difference resource on the server.... depends on which fileset installed.

besides SAM, command /etc/opt/resmon/lbin/monconfig can be used to configure the monitor.

GOOD LUCK!!

[Steven E. Protter]

Shalom Shah,

General: EMS, configurable by SAM (thats the only way I ever configured it) can use the cstm tool to check on the health of the system.

cstm is an option when setting up EMS monitoring.

You need to make sure Online Diagnostic tools (which inlcude cstm) are up to date on your system.

SEP

[Andrew Merritt_2]

Some of the above comments are a little confused, I'm afraid.

EMS is the Event Monitoring Service, and is a framework which delivers notifications via email, SNMP and log files. There are several packages that use this.

One of these is the Resource Management in SAM (rather confusingly, this option is also called Event Monitoring Service). It monitors resources such a free disk space, status of devices (UP or DOWN), kernel resources, etc, and sends notifications when thresholds are reached. It has nothing to do with cstm.

Another is the EMS Hardware Monitors; these are part of the OnlineDiags package. These monitors report failures and other problems with the hardware using EMS to deliver the events. 'monconfig' is used to configure these. Each monitor looks after a particular type of hardware component(disks, CPU, memory, etc.), and by a combination of polling the status of the hardware and having events reported by the device driver (for some monitors it's both, for others it's just one method) report any problems. Critical or Serious events from a particular component will lead to that component being marked as DOWN (which would lead to an EMS event from the corresponding Resource Management path, if that has been configured in SAM).

cstm is one of the three interfaces to STM. 'cstm' is a character based, command line type interface. 'mstm' is a curses based full screen interface, and 'xstm' is an X windows interface. STM is also part of the OnlineDiags package. It allows various tools to be run to determine the status of hardware components on the system.

There is not a lot of configuration needed once the OnlineDiags are installed; the monitors should be running and reporting events by default to /var/opt/resmon/log/event.log, and Serious and Critical events to syslog and via email to the root user. STM should also work, for the root user.

http://www.docs.hp.com/en/diag.html has more information about the OnlineDiags.

The latest versions are listed here - http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

You can also go to http://www.software.hp.com and then type "B6191AAE" in the search box to find the latest for download.

http://docs.hp.com/en/diag/stm/stm_ptch.htm shows the latest patches, which should be applied once you've installed a particular version.

Andrew