Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

ADD A NEW IDEA

Network Management System (NMS)

Showing 98

SNMP Polling inside unique contexts should be fixed. Never worked despite having some functionality already built in. Very important to us to monitor BGP Peers in unique contexts.

Routing tables are segregated based on VRF. Sevone NMS only able to see BGP Peering in Default VRF/ Default CONTEXT. This means we are unable to see bgp peers drop to remote networks. This has vast consequences for us. This is no good! Please refe...
29 days ago in SevOne / Network Management System (NMS) 0 Future consideration

IBM SevOne NMS Alert Dashboard needs to display the Metadata column

The end-customers wants to display the Metadata field at the same time when he sees a problematic Object or Device on the Alert Dashboard (because there are fields such as the unit used and the contact person in the Metadata) The end-customer want...
over 1 year ago in SevOne / Network Management System (NMS) 5 Future consideration

Alert for device discovery

When the devices were not being discovered properly the user is unable to find out until unless they are facing any issue. So, I'm thinking to have an alert for the device discovery, which helps to notify the user when the discovery was stuck. Thi...
17 days ago in SevOne / Network Management System (NMS) 0 Future consideration

Device Type Classification in SevOne REST API

My team owns IBM CP4AIOPS ASM observer that responsible for resource topology discovery. We do have an integration with SevOne, called SevOne Observer. At the moment. I have a request from StarHub and EastLink on the capability for AIOPs to classi...
7 months ago in SevOne / Network Management System (NMS) 4 Future consideration

To allow NMS user to run device discovery without granting 'Device Edit' privilege

To allow NMS user to run device discovery without granting 'Device Edit' privilege
2 months ago in SevOne / Network Management System (NMS) 0 Future consideration

IBM SevOne NMS upgrades should allow for limit or throttling of ssh connections

During a production upgrade for IBM SevOne NMS, a Palo Alto Networks firewall adaptive security policy automatically blocked traffic between IBM SevOne NPM peers due to excessive network traffic on TCP port 22. SevOne NPM uses Ansible to perform c...
20 days ago in SevOne / Network Management System (NMS) 2 Not under consideration

I want the SNMP Working Yes/No filter to be real-time - not based on the last successful discovery

When I set the SNMP Yes / Working No filter, I expect the result to be accurate - not based on the result of the last successful discovery. I should not have to manually check the results of the filter to see if they accurate.
about 2 months ago in SevOne / Network Management System (NMS) 0 Future consideration

Add on new basic messaging protocol "MQTT" to NMS.

IOT is growing in the IT infrastructure monitoring and the end customer will hope he can consolidation monitor over all. MQTT is growing to IOT standard protocol and the other brands NMS have been added MQTT in their protocol. For example: Zabbix....
about 1 year ago in SevOne / Network Management System (NMS) 2 Future consideration

Update SNMP (Under TRAPD) to accept more SNMPV3 protocols

Within SevOne's SNMPV3 setup, (TrapD) only the following protocols are allowed to accept traps generated by SNMP : DES, AES128, AES192, and AES256. 3DES encryption is not a "supported protocol" to accept generated SNMP Traps inbound into SevOne......
28 days ago in SevOne / Network Management System (NMS) 0 Under review

Expose/Create a SevOne metadata field which contains the name of the SevOne NMS which is polling the device.

The Peer/Poller metadata field can be used to create device groups. Currently in the DI metadata report, there is a metadata field called the Peer Name / Poller Name which contains the name of the NMS system which 'owns' the device. However this m...
28 days ago in SevOne / Network Management System (NMS) 1 Needs more information