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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
In our environment all the DB2 db's are running in GCP cloud environment which are enabled with HADR along with TSA. We use network tie breaker in our environment, recently we faced HADR split brain issue due to network issue and raised case with IBM (TS003746592) for the same.
Below are the response from IBM for our issue: This is a known issue/limitation of the network tiebreaker, RSCT uses UDP for heartbeats, the network tiebreaker uses ICMP, when there is a network problem and the network recovers the ICMP protocol is brought up before UDP is , so the tiebreaker can be reserved while the UDP (RSCT heartbeat) is still failing. This ends up with a domain_merge The solution is that: 1) don't use network tiebreaker, use arbitrator node, NFS, Cloud or disk tiebreaker instead 2) don't have network failures 3) increase the period/sensitivity so that longer network outages are not reported by RSCT
many DB2 db's are critical in our environment so we need to have robust solution for this issue. We prefer to change our TSA tie breaker from network to cloud. But for cloud IBM provided solution is for AWS. We need same solution for GCP, We checked the same with google and they told us to inform IBM regarding same. This is the reason i raised this case. We need to your help regarding this solution. Please let us know if any other details required.
Do not place IBM confidential, company confidential, or personal information into any field.