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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
A device post discovery is always defined as a particular device type, such as F5, Cisco ASA, etc. Device Group Membership rules should allow for the ability to use Device Type as a means of membership. Currently I am forced to define what the OID is that defines that product. As a consumer of SevOne NMS I expect SevOne to keep up with the latest Product OID's, and update the Device Types.
So regardless of what the latest Cisco ASA Product OID is, it would also be added to my Cisco ASA Product group. This removes the need for me the customer, t constantly go in and update Device Grouping rules.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
To clarify, you want to be able to generate a report of device types (vendor/model/revision) by customer?
Hey Marcus, this more of an ask of that auto-generated grouping based on discovered OIDs like sysDescr and sysObejctId right?
Today you can build device groups referencing them today, but I'm guessing the ask based on our previous convo is more about that being auto-generated groupings rather than that pre-conception and cognitive burden being on the admin right?
Hey Marcus, I understand your ask about making it easier to build Device Groups based on inputs like OIDs, and would like to get a better idea how these Device Groups would be used in the example you provided.