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)
Add support for SHA256 encryption for SNMPv3 discovery and polling in ITNM
We all need a good hash encryption algorithm in SNMPv3. SHA 1 is likely to be broken and all the NE vendors and security policies are moving to SHA2. We opened the case TS007203260 recently and we were told that SHA256 support is not planned for t...
Better control over snmp polling for big network devices
ITNM has two different strategies for polling interfaces depending on the use of a polling filter: - Strategy 1 (when no polling filter is defined): poll all OIDs for each interface. - Strategy 2 (when a polling filter is defined): group multiple ...
Process to clean up old entities from active devices
Once a device is discovered bu ITNM, it creates many entities in NCIM database, representing the device, interfaces etc. If any of those entities are not valid anymore (e.g., one of the interfaces is disabled), it is not deleted from the database....
ITNM installs the client to connect to database for access the NCIM tables. For Oracle, having it installed and upgraded from 184.108.40.206 to 220.127.116.11 (with many steps in-between over the years), I see two clients at $NCHOME/precision/platform/linux2x8...
ITNM 18.104.22.168:Alcatel SAM 5620 Collector : Connect to Multiple EMS's
We are using Alcatel5620Sam Java collector to connect to single EMS and able to download topology successfully. Currently in customer environment, Nokia NFM-P EMS has been configured with High Availability so that any of the one instance will be i...
When scanning vulnereability of our application server(s), we've noticed that JBoss 4.x is no longer supported by Red Hat, which caused vulnerability flags. We've been informed that JBoss itself is tightly integrated with TNPMW application, so upg...
ITNM to support Layer 2 connection on ZTE C300M (MSAN) devices
we need to get Layer 2 connectivity for device 'ZTE C300M device' with OID 22.214.171.124.4.1.3902.1082.1001.6000.4.2 so that it will be supported in ITNM as per case TS001982826, where support confirmed that the layer 2 connection is not supported and w...
ITNM to support Layer 2 connection on Huawei Integrated Access (MSAN) devices
we need to get Layer 2 connectivity for device 'Huawei Integrated Access (MSAN) MA5600 device' with OID 126.96.36.199.4.1.2011.2.80.8 so that it will be supported in ITNM as per case TS001982826, where support confirmed that the layer 2 connection is no...
Do not place IBM confidential, company confidential, or personal information into any field.