This is an IBM Automation portal for Cloud Management and AIOps products. 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
Start / StopCommand is not issued to the resources with Unknown state, during start / stop of resource group or takeover.
"StartCommand / StopCommand is not issued to the resources with Unknown state, during starting / stopping of resource group or takeover"
This request comes from the PMR - 04264,616,760 The request is for a change to issue StartCommand / StopCommand to Unknown resources during the start / stop of a resource group or takeover.
At high workload on the system, Unknown will likely to occur due to a time-out of the MoniorCommand and also likely to cause a takeover. Especially at the time of takeover, if stop command is not issued to the Unknown resources, the resources will run on both systems, which may cause for example, damage to the file system is mounted. The TSA policy that TSA does not cause any action to the Unknown resources is no problem if system is running normally, care is needed during takeover.
Because there is a risk of damage when critical resource runs at the same time in both systems, we usually include a command to force shutdown of the resource in the StopCommand to avoid the risk. Therefore issuing a StopCommand even for Unknown resources would be able to protect critical resources.
Do not place IBM confidential, company confidential, or personal information into any field.