<?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: cmmodpkg -n nodename -e pkg name in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700672#M249269</link>
    <description>i Zungwon,&lt;BR /&gt;&lt;BR /&gt;cmmod pkg -e  Enables package itching.  This may cause a currently &lt;BR /&gt;down package to be started on a running node (according&lt;BR /&gt;to its failover policy).  If the -n option is given,&lt;BR /&gt;package switching will be enabled only for the speci-&lt;BR /&gt;fied node(s); otherwise, switching will be enabled glo-&lt;BR /&gt;bally.  This will not cause the package to move if the&lt;BR /&gt;package is currently running elsewhere.&lt;BR /&gt;&lt;BR /&gt;and you can findout this in the package switching policy in the package configuraion files.&lt;BR /&gt;&lt;BR /&gt;example: #&lt;BR /&gt;&lt;BR /&gt;# Enter the value for AUTO_RUN. Possible values are YES and NO.&lt;BR /&gt;# The default for AUTO_RUN is YES. When the cluster is started the&lt;BR /&gt;# package will be automatically started. In the event of a failure the&lt;BR /&gt;# package will be started on an adoptive node. Adjust as necessary.&lt;BR /&gt;#&lt;BR /&gt;# AUTO_RUN replaces obsolete PKG_SWITCHING_ENABLED.&lt;BR /&gt;&lt;BR /&gt;AUTO_RUN   YES&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;you can cahnge it to no if you don;t want the switching&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;tvs</description>
    <pubDate>Mon, 02 Jan 2006 05:27:48 GMT</pubDate>
    <dc:creator>Tvs</dc:creator>
    <dc:date>2006-01-02T05:27:48Z</dc:date>
    <item>
      <title>cmmodpkg -n nodename -e pkg name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700671#M249268</link>
      <description>there is two conde configured MC/Serviceguard.&lt;BR /&gt;When oracle is stopped in one node as type cmhaltnode -f node1, the pakage connected with oracle package move to node2.&lt;BR /&gt;When I try to back to onde node1, I typed as cmmodpkg -n node1 -e ora_pkg1 and then cmrunpkg -n imis1 ora_pkg1.&lt;BR /&gt;I want to know where this cmmodpkg -n nodename -e pkg name option is configured to modify as auto.</description>
      <pubDate>Mon, 02 Jan 2006 01:14:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700671#M249268</guid>
      <dc:creator>???_185</dc:creator>
      <dc:date>2006-01-02T01:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: cmmodpkg -n nodename -e pkg name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700672#M249269</link>
      <description>i Zungwon,&lt;BR /&gt;&lt;BR /&gt;cmmod pkg -e  Enables package itching.  This may cause a currently &lt;BR /&gt;down package to be started on a running node (according&lt;BR /&gt;to its failover policy).  If the -n option is given,&lt;BR /&gt;package switching will be enabled only for the speci-&lt;BR /&gt;fied node(s); otherwise, switching will be enabled glo-&lt;BR /&gt;bally.  This will not cause the package to move if the&lt;BR /&gt;package is currently running elsewhere.&lt;BR /&gt;&lt;BR /&gt;and you can findout this in the package switching policy in the package configuraion files.&lt;BR /&gt;&lt;BR /&gt;example: #&lt;BR /&gt;&lt;BR /&gt;# Enter the value for AUTO_RUN. Possible values are YES and NO.&lt;BR /&gt;# The default for AUTO_RUN is YES. When the cluster is started the&lt;BR /&gt;# package will be automatically started. In the event of a failure the&lt;BR /&gt;# package will be started on an adoptive node. Adjust as necessary.&lt;BR /&gt;#&lt;BR /&gt;# AUTO_RUN replaces obsolete PKG_SWITCHING_ENABLED.&lt;BR /&gt;&lt;BR /&gt;AUTO_RUN   YES&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;you can cahnge it to no if you don;t want the switching&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;tvs</description>
      <pubDate>Mon, 02 Jan 2006 05:27:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700672#M249269</guid>
      <dc:creator>Tvs</dc:creator>
      <dc:date>2006-01-02T05:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: cmmodpkg -n nodename -e pkg name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700673#M249270</link>
      <description>But when the pakage of node1 was downed, node1 move to node2.the configuration is same like AUTO_RUN YES&lt;BR /&gt;and then, I have forced node2 to move to node1 as cmhalt pkge.&lt;BR /&gt;But it didn't.&lt;BR /&gt;May be connected with AILBACK_POLICY=MANUAL?</description>
      <pubDate>Mon, 02 Jan 2006 19:39:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700673#M249270</guid>
      <dc:creator>???_185</dc:creator>
      <dc:date>2006-01-02T19:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: cmmodpkg -n nodename -e pkg name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700674#M249271</link>
      <description>Hi ZungWon,&lt;BR /&gt;&lt;BR /&gt;Yup, the FAILBACK_POLICY need to be set with MANUAL.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;AW</description>
      <pubDate>Mon, 02 Jan 2006 19:51:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmmodpkg-n-nodename-e-pkg-name/m-p/3700674#M249271</guid>
      <dc:creator>Adisuria Wangsadinata_1</dc:creator>
      <dc:date>2006-01-02T19:51:25Z</dc:date>
    </item>
  </channel>
</rss>

