Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Can an option be given the user performing to switch to specify he/she wants to perform a permanent/temporary failover? The default action can be temporary, with an additional option in case permanent failover is intended.
This behavior is by design for this distinction:
1. Manual `switchmgr` is intended to be TEMPORARY. The `switchmgr` command is typically used for planned maintenance, short-term testing, or temporary resource shifting. When executed manually, the system assumes the switch to the new server is **transient** and that the original MDM will soon resume its role. If the workstation definitions (which reside in the database, the **long-term configuration**) were automatically updated, the administrator would be forced to manually edit the definitions *again* when switching back to the preferred, original MDM.
2. Automatic Failover is intended to be PERMANENT (or long-term recovery). In a real automatic failover scenario (Disaster Recovery), the system assumes the primary MDM is permanently down or unavailable for an extended period. Therefore, the new server must take over the **long-term MDM identity**, justifying the automatic update to the workstation definitions in the database.