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:
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
Control Desk
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)
Tivoli Application Dependency Discovery Manager - TADDM
If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Operations Management
Product - Tivoli Netcool Performance Manager
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Operations
Product - Tivoli Netcool Performance Manager
Attachments Open full size
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - ITSM Operations
Product - Tivoli Netcool Performance Manager
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Performance Monitoring
Product - Tivoli Netcool Performance Manager
Attachments Open full size
This RFE is now considered resolved.
Tom Randles
TNPM tech pack product manager
randles@ie.ibm.com
Attachments Open full size
IBM provided the current invariant as a working example that pre-dates when Cisco added MPLS interfaces to the ifIndex table. Customers of TNPM often alter our match/discovery formulas to improve/alter invariants, or discovery profiles.
Note that a product fix to address this will not be possible, due to the disruptive impact such a modification would have on our current installed base for this pack.
TNPM support have already made recommendations as to how this invariant should be changed in order to discovery these virtual interfaces correctly. These custom modifications do require you to be able to test and validate within your own test environment before deploying in your end-customer’s environment.
We advise caution in any manipulation of invariant, as changing the invariant can cause the previous instances to be "burned" (removed with prejudice):
1. Current sub-element will be "burned" which means the su-element that is currently collecting will be completely disabled
2. The same sub-element will be re-discovered but with a different dbIndex. In other words, there will not be any continuity in charts, between the "new" and "old" sub-elements
3. The historical data will be still available under the "old" sub-element.
We continue to recommend our MPLS pack to understand how the data is passed within your environment. We should investigate means by which we can validate this.
Tom Randles
TNPM tech pack product manager
Attachments Open full size