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)
Interface types are not distinguished in manual connection configuration
During the configuration of manual connections in layer 1, the problem has been when creating connections in layer 1 and the confusion occurs because the devices in the discovery have the same Display Label in different types of interfaces, for example cases in which mpls and ethernet they have the same Display Label.
It is necessary to be able to distinguish what type of interfaces they correspond to, in our case all layer 1 is done manually and many devices have this case and its correction is complicated.
1206 / 5000
At AT&T, one of the main features that Network Manager is given is to generate the layer 1 topology of the devices on the network. These daily configurations are done with the help of Network Manager to add manual connections from the hop view.
Currently, a little more than 5800 devices have been discovered and all must have their topology configured in Layer 1, daily there are new devices and devices that are removed due to updates on the network.
As an example of this case, there is a device with the following interfaces:
IFINDEX = 2, DISPLAYLABEL = [Te0/0/1], IFTYPESTRING = ethernet-csmacd
IFINDEX = 18, DISPLAYLABEL = [Te0/0/1], IFTYPESTRING = mpls
When trying to add a new manual connection with the ethernet interface (Layer 1) of the device, in the list of options we find that there are two interfaces [Te0/0/1], this generates confusion because it is not known which one to choose. At the end we can only validate once the connection has been added to list the device connections. If it is not correct, the connection is deleted and the connection is added again using the following option that appears duplicated.
Do not place IBM confidential, company confidential, or personal information into any field.