This is an IBM Automation portal for Cloud Management 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
The Coriant G30 device can be discovered but all elements like it’s interfaces are not discovered, only chassis level and identify as network device i mean only layer 2 and no layer 3 also the neighbor device it connected to also recognised but li...
For device discovery when CDP and LLDP are disabled, add support for non-LACP link aggregation. in order to obtain all required link-layer data like link aggregation membership data obtained at Layer 2
Display 'connected to' details against the physical interface members of a LAG
The display of interface details of an bundled interface (LAG) the 'connected to' information is not available on the physical interface members. This would show interface connection in more details than only on the aggregated entity
Include the cross-domain topology in the ncp_dla exported file
though the NCIM have cross-domain connections populated using cross-domain stitching. The ncp_dla does not fetch the cross-domain topology in the exported file. the cross-domain topology export is not implemented in ncp_dla.
Make Component discovery of fabric extender consistent
For Cisco Nexus Fabric extenders(FEX) attached to Nexus N9K switches (even with recent firmware), sometimes fabric extender elements were not discovered and the chassis element was not discovered. on other hosts, only the chassis element but no fa...
Improve the ITNM mustgather script and provide in the code with future fixpack releases
Currently the itnm_data.pl mustgather script is provided in a technote available for download here: https://www.ibm.com/support/pages/collect-data-ibm-tivoli-network-manager-ip We would like to see this included in the code so that it is available...
ITNM agents/stichers to discover Cisco Fabric Extender (FEX) data
Today FEX information that can be obtained from SNMP requests from Cisco devices is being ignored by the official IBM discovery agents and stitchers. Since this is official, standard data from Cisco devices, I see as counter-productive to have cus...
Do not place IBM confidential, company confidential, or personal information into any field.