<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Serviceguard notification in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848959#M274533</link>
    <description>That is really the role of the package control scripts and they are as powerful or as wimpy as you choose to make them. My approach is rather simple. I simply send a message to OpenView Operations when the package starts up indicating the static hostname that the package is now running on. This does mean that you get this message in the OV/O Message Browser when a package is started normally but you also get them when a packages failsover to another node.</description>
    <pubDate>Wed, 23 Aug 2006 10:23:47 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2006-08-23T10:23:47Z</dc:date>
    <item>
      <title>Serviceguard notification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848957#M274531</link>
      <description>How does Serviceguard notify the system admin that a failover has occurred?  Is there a system console message or is there an SNMP/WBEM trap that is sent to HPSIM?&lt;BR /&gt;&lt;BR /&gt;Thanx in advance for your help.</description>
      <pubDate>Wed, 23 Aug 2006 10:09:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848957#M274531</guid>
      <dc:creator>Mark A Bradford</dc:creator>
      <dc:date>2006-08-23T10:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard notification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848958#M274532</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;It does not notify anyone by default.&lt;BR /&gt;&lt;BR /&gt;You can write a monitor script that does this and build it into the package. Its the responsibility of the admin to create such things.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 23 Aug 2006 10:16:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848958#M274532</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-23T10:16:40Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard notification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848959#M274533</link>
      <description>That is really the role of the package control scripts and they are as powerful or as wimpy as you choose to make them. My approach is rather simple. I simply send a message to OpenView Operations when the package starts up indicating the static hostname that the package is now running on. This does mean that you get this message in the OV/O Message Browser when a package is started normally but you also get them when a packages failsover to another node.</description>
      <pubDate>Wed, 23 Aug 2006 10:23:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848959#M274533</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-08-23T10:23:47Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard notification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848960#M274534</link>
      <description>Hi Mark,&lt;BR /&gt;&lt;BR /&gt;I setup a email address in the package cntl file to send email notifcation when the package is stop or started. make entry for both stop and start.&lt;BR /&gt;&lt;BR /&gt;echo "Starting GEX"&lt;BR /&gt;       /h/EC/progs/debxctl start&lt;BR /&gt;&lt;BR /&gt;mailx -s "gex_pkg is being started on `hostname` " xxxxxx.xxxxxxx@dla.XXX &amp;lt; /dev/null</description>
      <pubDate>Wed, 23 Aug 2006 10:55:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848960#M274534</guid>
      <dc:creator>Sp4admin</dc:creator>
      <dc:date>2006-08-23T10:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard notification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848961#M274535</link>
      <description>Mark,&lt;BR /&gt;&lt;BR /&gt;ServiceGuard sends snmp traps , yes.&lt;BR /&gt;You can add the SNMP monitoring system to the file /etc/snmpd.conf.&lt;BR /&gt;For example ServiceGuard Manager does this if you want to.&lt;BR /&gt;&lt;BR /&gt;Look at this for example:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B8325-90036/ch01s04.html" target="_blank"&gt;http://docs.hp.com/en/B8325-90036/ch01s04.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Klaas.</description>
      <pubDate>Thu, 24 Aug 2006 01:34:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-notification/m-p/3848961#M274535</guid>
      <dc:creator>Klaas D. Eenkhoorn</dc:creator>
      <dc:date>2006-08-24T01:34:53Z</dc:date>
    </item>
  </channel>
</rss>

