EMS Monitors

[Duncan Edmonstone]

Anyone know where I can get some info and config guides on the types of resources that can be monitored under the following resource classes that are returned by 'resls /' :

/StorageAreaNetwork
/rdbms

The other resource classes are discussed in the HA Monitors manual and EMS User guide, but I can find no details on these resource classes.

Thanks

Duncan

[Christopher Caldwell · Accepted solution]

http://docs.hp.com/hpux/ha/index.html

Look at the section called
Event Monitoring Service and HA Monitors

There's a number of manuals.

[Duncan Edmonstone]

Thanks - couldn't see for looking!

Anyone with actual experience of using these monitors out there?

e.g. If I configure a MCSG Package with a dependency on two databases dbA and dbB located on other servers:

What do my resource entries in my package configuration file look like?

Presumably I have to tell rdbmsmond to look on another server by using the '-h' argument with rdbmsmond when configuring it in /etc/opt/resmon/dictionary/mibmond.dict - how can I set this up to look at two seperate servers?
What if those servers are also ina cluster?

If one of the monitored databases fails, the package will fail-over - but if the monitored database hasn't restarted, presumably the package will be stopped completely - is there any way for ServiceGuard to restart the package when the other database re-starts?

I appreciate all this can be acheieved just using scripts, but I am trying to take on-board the inclusion of EMS monitors within ServiceGuard - am I just pushing the use of EMS too hard on this?

Incidentally what I'm really looking for an answer to is an elegant solution to the idea of 'inter-package dependencies' that Veritas Cluster Server uses (i.e. one package can be dependent on another)

[melvyn burnard]

Just for information, this precise topic and how to do it is covered in the MC/ServiceGuard II course, available from HP Education Centres.

http://education.hp.com/datasheets/h4310s.pdf

[Christopher Caldwell]

I'd build package A on host A with EMS running on A - it would monitor the database status an tie into MC/Service Guard.

I'd build package B on host B with EMS running on B - it would monitor the database status an tie into MC/Service Guard.

Package A could run on host A or B; package B could run on host A or B.

On application failure (determined in EMS), the package on the failed node would be configured to move to the running node.

Is that what you're looking for?

[Chris Melick]

Duncan,

Did you ever find the solution you were "really" after, inter-package-dependencies like VCS offers? I too am looking for that same solution.

Thanks,
Chris

[Duncan Edmonstone]

No, not directly - I just use scripts to add package dependencies - not too complex to do...

A while ago I saw a note saying that proper package dependencies would be part of SG 11.17 - but I don't know if thats still the case, or even when 11.17 is due...

HTH

Duncan