EMS configuration

[John Cattanach]

Hi,
We're shipping a product with our own EMS target application (c.f. tcp_target.c in resmon devkit).
My question, is there any way to automate the configuration of EMS monitors (i.e. UDP host + port, poll interval). At the moment we're doing this by hand, but once we start shipping multiple machines that will lose it's novelty value.
Any help appreciated,
John Cattanach

[Anonymous]

Hi John,

what do you need to configure for your EMS monitor?
Point behind that question: as long as you just read from EMS' cfg files you may want to automate changes to these files.

Few months ago I started to shell-script sth like this (currently unfinished and not waterproof)- let me know if that's what you're looking for.

RGDS
Thomas

[John Cattanach]

Hi Thomas.
Some details: I'm configuring EMS to send state changes from multiple resource monitors to a specific UDP port. I haven't managed to find any relevant cfg files to do this, so anything you can provide could well help. Nearest I could find was /etc/opt/resmon/persistent but looked like a distinctly private interface.
btw, running hp/ux 11.0, ems ?
Thanks,
John

[Anonymous]

q1 Can you walk me through your manual configuration change? (sounds like some SAM-resmon clicking...)

BTW q2 are your config changes permanent? (ie survive a reboot- I had some probs with that, so I started to play with d=/var/stm/config/tools/monitor/*cfg)

I'd say one may try to cp $d /tmp then change EMS' config and diff $d with our copies- just to see if that cfg-file approach is what you're looking for.

Probably you find that gif useful- see file att'ed.

cu Thomas

[John Cattanach]

Hi Thomas.
What I'm doing currently is SAM, resource management, EMS. Then Add Monitoring Request for each resource, defining UDP port.
I had a look around the files you mentioned, but the only one that seems to get updated when I add a request is /etc/opt/resmon/persistence/m. (these files have text matching my monitor request parameters, apart from the comments).
Regarding persistence, yes the monitor requests have survived a couple reboots, though they seem to disappear if the allied resource monitor crashes.
John

[Anonymous]

hm, one may check /var/sam/log/samlog if the user interface leaves some information what it does (eg using /usr/sam/bin/samlog_viewer) ...but not all user interfaces (*.ui) do that.

Good luck- and let us now if you found a way ;-)
RGDS, Thomas