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)
creating a Domain should not automatically switch on ip_forwarding
creating a TSAMP-Domain causes unasked ip_forwarding to "on" even though it is not necessary if CG(s) are all in the same subnet. RSCT needs the function "Loose Source Routing": A simple answer for now is that RSCT uses LSR to deal with communication between cluster nodes when multiple networks are impaired, and there is no direct route between two nodes, but there are indirect routes available because of neighbors that both those node share. (This means it is useless on a 2-node cluster.) "IP forwarding" is required for LSR to function -- if it is disabled, LSR will not work.
Our security policy will be monitored periodically from security staff and other organisations like "BaFin". So in our case ip_forwarding is forbidden for our servers for security reasons. ip_forwarding to ON causes that every Server acts as a router which will have affect to security. While creating a TSAMP-Domain the user will not be informed that ip_forwaring will be switched on. This behavior must be changed. It should be an option during creating a Domain or should be a part of the TSAMP-Policy, so it could be switched off. The default should be "off".
Do not place IBM confidential, company confidential, or personal information into any field.