<?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: MC Service Guard in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073415#M559013</link>
    <description>&lt;P&gt;Are the two nodes on the same Superdome? If so, ServiceGuard won't help keep things going.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Or is your goal to just monitor database(s) and apps and change to the other node when things aren't working?&lt;/P&gt;&lt;P&gt;A big part of the setup will be to define failure modes which can be handled with failover. For instance, if the app/db fails due to a full filesystem, the filesystem cannot be part of the shared storage or the same failure will exist on the other node. Similar problems might relate to kernel parameters that are exceeded. Some kernel limits will be new on the other node and the apps will start OK, others may cause the app/db to fail as the limit does not change on the second node.&lt;/P&gt;&lt;P&gt;There are lots of docs at hpe.com for designing an SG environment and some good paper books on the subject. Mr. Google will be useful but only choose docs from hpe.com.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Dec 2019 19:25:52 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2019-12-18T19:25:52Z</dc:date>
    <item>
      <title>MC Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073306#M559010</link>
      <description>&lt;P&gt;&lt;FONT color="#000000"&gt;Hi Guys,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;I'm trying to do a cluster setup on two nodes, and need assistance with that. Can someone share the step by step plan or any guidance for that? Both the servers are HP-UX 11.31 virtual machines running on Superdome. Thanks.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ghouse Bagwan.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 07:13:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073306#M559010</guid>
      <dc:creator>ghousebagwan</dc:creator>
      <dc:date>2019-12-18T07:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073316#M559011</link>
      <description>&lt;P&gt;Serviceguard is complex - and what you require is often not a straightforward list of commands as you have to consider what you are actually trying to achieve and your own circumstances, so my real advice is to RTFM:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&amp;amp;docId=emr_na-a00062147en_us&amp;amp;withFrame" target="_blank"&gt;https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&amp;amp;docId=emr_na-a00062147en_us&amp;amp;withFrame&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you really want to jump straight in to creating the cluster (I don't advise it), then go straight to the "Configuring the cluster" section on p237&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 08:01:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073316#M559011</guid>
      <dc:creator>Duncan Edmonstone</dc:creator>
      <dc:date>2019-12-18T08:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073321#M559012</link>
      <description>&lt;P&gt;Another question is if you want to have serviceguard for the application or just for the VM itself.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 08:46:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073321#M559012</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2019-12-18T08:46:31Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073415#M559013</link>
      <description>&lt;P&gt;Are the two nodes on the same Superdome? If so, ServiceGuard won't help keep things going.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Or is your goal to just monitor database(s) and apps and change to the other node when things aren't working?&lt;/P&gt;&lt;P&gt;A big part of the setup will be to define failure modes which can be handled with failover. For instance, if the app/db fails due to a full filesystem, the filesystem cannot be part of the shared storage or the same failure will exist on the other node. Similar problems might relate to kernel parameters that are exceeded. Some kernel limits will be new on the other node and the apps will start OK, others may cause the app/db to fail as the limit does not change on the second node.&lt;/P&gt;&lt;P&gt;There are lots of docs at hpe.com for designing an SG environment and some good paper books on the subject. Mr. Google will be useful but only choose docs from hpe.com.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 19:25:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073415#M559013</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2019-12-18T19:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073448#M559014</link>
      <description>&lt;P&gt;Hi Torsten,&lt;/P&gt;&lt;P&gt;I want to have it for Application .&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2019 07:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073448#M559014</guid>
      <dc:creator>ghousebagwan</dc:creator>
      <dc:date>2019-12-19T07:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073450#M559015</link>
      <description>&lt;P&gt;Hi Bill,&lt;/P&gt;&lt;P&gt;Both the nodes are hosted on different superdomes. I want the node2 as failover when we have any failure(any hardware/software creash) state on node1.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2019 07:41:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard/m-p/7073450#M559015</guid>
      <dc:creator>ghousebagwan</dc:creator>
      <dc:date>2019-12-19T07:41:06Z</dc:date>
    </item>
  </channel>
</rss>

