Operating System - HP-UX
1851693 Members
3533 Online
104061 Solutions
New Discussion

Re: cmmodpkg -n nodename -e pkg name

 
???_185
Regular Advisor

cmmodpkg -n nodename -e pkg name

there is two conde configured MC/Serviceguard.
When oracle is stopped in one node as type cmhaltnode -f node1, the pakage connected with oracle package move to node2.
When I try to back to onde node1, I typed as cmmodpkg -n node1 -e ora_pkg1 and then cmrunpkg -n imis1 ora_pkg1.
I want to know where this cmmodpkg -n nodename -e pkg name option is configured to modify as auto.
3 REPLIES 3
Tvs
Regular Advisor

Re: cmmodpkg -n nodename -e pkg name

i Zungwon,

cmmod pkg -e Enables package itching. This may cause a currently
down package to be started on a running node (according
to its failover policy). If the -n option is given,
package switching will be enabled only for the speci-
fied node(s); otherwise, switching will be enabled glo-
bally. This will not cause the package to move if the
package is currently running elsewhere.

and you can findout this in the package switching policy in the package configuraion files.

example: #

# Enter the value for AUTO_RUN. Possible values are YES and NO.
# The default for AUTO_RUN is YES. When the cluster is started the
# package will be automatically started. In the event of a failure the
# package will be started on an adoptive node. Adjust as necessary.
#
# AUTO_RUN replaces obsolete PKG_SWITCHING_ENABLED.

AUTO_RUN YES


you can cahnge it to no if you don;t want the switching

regards

tvs
???_185
Regular Advisor

Re: cmmodpkg -n nodename -e pkg name

But when the pakage of node1 was downed, node1 move to node2.the configuration is same like AUTO_RUN YES
and then, I have forced node2 to move to node1 as cmhalt pkge.
But it didn't.
May be connected with AILBACK_POLICY=MANUAL?
Adisuria Wangsadinata_1
Honored Contributor

Re: cmmodpkg -n nodename -e pkg name

Hi ZungWon,

Yup, the FAILBACK_POLICY need to be set with MANUAL.

Cheers,
AW
now working, next not working ... that's unix