Does diagmond integrate wiht EMS or WBEM?

[Tom Ward_1]

Diagmond dies sometimes due to network scans. I'd like to configure it for local access only, but I don't know how it plays into other monitoring products from HP. Does anyone know?

[Michael Steele_2 · Accepted solution]

Hi

'diagmond' is the STM daemon.
'EMS' is installed at the same time as STM and is 'snmp' based.
'WBEM' is bound together more closely to CIM server and Itanium architecture, but all are apart of the online diagnostics bundle.

Here's a OK discussion:

http://h71028.www7.hp.com/enterprise/cache/11380-0-0-225-121.html

[Tom Ward_1]

Thank you for the quick reply. I've worked with STM before, but don't know anything about EMS or WBEM. I was worried that one of them might rely on STM. Sounds like I'm safe to disable network access on them. Thanks.

[Steven E. Protter]

Shalom,

>>
Thank you for the quick reply. I've worked with STM before, but don't know anything about EMS or WBEM.
<<

EMS is a good emergency notification system. You can configure it to cut you an email when things happen you should not about.

WBEM is explained better by HP documentation.
http://docs.hp.com/en/5990-6739/ch05s05.html

SEP

[Tom Ward_1]

What about ISEE, does that need network access to diagmond?

[Michael Steele_2]

ISEE uses STM and other Online Diagnostics monitors. ISEE is the phone home utility, you know, an HP CE meets you Tuesday morning to replace a disk. So, yes, ISEE needs all of online diags for HP analysis.

[Tom Ward_1]

ISEE connects to the servers it monitors via port 5060 on a process called "mad".

There is a tie in from ISEE to EMS, but I could find nothing about it connecting to diagmond remotely. This is what I was after.

BTW, ISEE goes end of life 31 Oct 09.