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)
Support hexstring datatype in ITNM event poll definitions or advanced polling
ITNM generic polls need to be able to report the values for common snmp datatypes, such as (especially) Hex-STRING. Today it seems that we can only specify text, int, and time in advanced polling or poll event description; OIDs with octet string datatypes are converted to ASCII by ITNM before we can see the original values. In particular, BGP-4 mibs encode IPv4 or IPv6 strings as hex-strings, and we need to be able to work backwards from a string such as this:
'74 33 1B 65' = '22.214.171.124' (Not 't3 e' – some of it is convertible, but where do you put the separations?!) or '20 01 02 18 40 00 50 00 00 00 00 00 00 00 01 89' = '2001:218:4000:5000:0:0:0:189' (not ' @')
To solve this problem, we would like to have a hex format string to include in the poll's event description, something like this:
I thought perhaps this was built in and just undocumented – but, no: IBM L3 told me I needed to open an RFE for this functionality.
For snmp polling, if the oid datatype is a hex-string, give us the hex-string.
Do not place IBM confidential, company confidential, or personal information into any field.