I put this question to AIX support and received a "that's not supported" answer.
Anyone got a workaround for this issue? Seems pretty basic.
Product or Service: POWERHA SYSTEMMIRROR V7.1 Technology Level1 7.1.1
.
Operating System: AIX
.
Problem title
How to prevent accidental cluster deletion from mksysb clones?
.
Problem description
The scenario: We have a working PowerHA 7.1 cluster running under AIX
7.1. We create a mksysb of one of the nodes and clone another separate
standalone node using NIM. The new standalone node gets a new IP
address, and a new name. We delete the cluster config from the
standalone node and it reaches out and deletes the cluster config from
what it thinks was its partner cluster node, which is still running in
the cluster. Ouch.
One workaround I see is to pollute the /etc/hosts file on the
standalone before attempting the cluster delete to redirect to a non-
existent node; perhaps 127.0.0.1.
I would prefer to exclude something on the mksysb creation. Can you
suggest a workaround?
Thanks.
Anyone got a workaround for this issue? Seems pretty basic.
Product or Service: POWERHA SYSTEMMIRROR V7.1 Technology Level1 7.1.1
.
Operating System: AIX
.
Problem title
How to prevent accidental cluster deletion from mksysb clones?
.
Problem description
The scenario: We have a working PowerHA 7.1 cluster running under AIX
7.1. We create a mksysb of one of the nodes and clone another separate
standalone node using NIM. The new standalone node gets a new IP
address, and a new name. We delete the cluster config from the
standalone node and it reaches out and deletes the cluster config from
what it thinks was its partner cluster node, which is still running in
the cluster. Ouch.
One workaround I see is to pollute the /etc/hosts file on the
standalone before attempting the cluster delete to redirect to a non-
existent node; perhaps 127.0.0.1.
I would prefer to exclude something on the mksysb creation. Can you
suggest a workaround?
Thanks.