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)
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 interfaces and do requests per OID.
For strategy 2, it means that if you have for instance 100 interfaces, and wanted to poll 2 OIDs, it will split the 100 interfaces into groups of 30 and then request OID1 for each group (with 30 varbinds on it) and then do the same for the second OID, etc. This however brings issues when a device has hundreds of interfaces and is not optimized for this kind of request (multiple interfaces per OID). The device may take a long time to answer each request and this causes timeouts in ITNM.
We would like to be able to finetune the polling in those situations, either by:
1) Deciding on which strategy to use even if a polling filter is defined
2) Deciding on how many parallel polling requests are triggered before next requests are made for same poll
3) Setting a custom polling timeout per device (so slower devices would not generate an alert while faster devices can continue to work as usual)
4) Have the option to set a delay between poll requests
These would allow to accomodate big devices and avoid timeout issues.
Do not place IBM confidential, company confidential, or personal information into any field.