This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Automation to activate / deactivate RPV server & client devices for PowerHA/XD managed GLVM VGs before after FS related tasks.
PowerHA/XD handles the RPV server & client devices on it's own. After the resource group take over has been completed, PowerHA/XD will:
- unconfigures the RPV server devices (puts them to defined state) belonging to the RG's volume groups on the active node
- unconfigures the RPV client devices (puts them to defined state) belonging to the RG's volume groups on the passive node
This works just fine and won't break the GLVM synchronization since the RPV clients coming from the passive node are available on the active node so the mirroring continues to happen on LVM level.
the problem only happens when it comes to perform FS tasks like, PowerHA/XD managed FS removal using clmgr CLI:
[g41p-a-00000370.az1.ash.cpc.ibm.com:/etc/dr-data] clmgr rm fs /dummy-fs
g41p-a-00000370: rmlv: Logical volume dummylv is removed.
cl_rmfs: Error executing clupdatevg datavg 00cb3f17170f8db5 on node g42pa00005861
ERROR: failed to delete "/dummy-fs".
same is the case while removing FS via smitty
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
g42pa00005861: rmlv: Logical volume testlv is removed.
cl_rmfs: Error executing clupdatevg datavg 00cce7f7690d007b on node g41p-a-00000370
In above case the active node was able to remove the FS but the passive not since the RPV client devices were not available on the remote node of the cluster since PowerHA/XD unconfigured them.
Do not place IBM confidential, company confidential, or personal information into any field.