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.

Status Not under consideration
Categories Performance
Created by Guest
Created on Jun 29, 2012

TNPM. Cisco Device Tech pack to discover virtual interfaces for MPLS devices when physical and virual interface have same ifName

Cisco Device Tech pack cannot discover virtual interfaces for MPLS Cisco devices. Because of that it is not possible to monitor any KPI for these interfaces. This means it is not possible to monitor even MIB II KPIs for these virtual interfaces, although you have installed MIB II tech pack. It is important to emphasize this RFE is not request for Cisco Device to monitor MPLS KPIs. It is request to monitor Cisco Device KPIs using Cisco Device tech pack, for Cisco MPLS devices.

Main problem here is AP~Cisco~Cisco_If_Stack_Dynamic_Discovery_Invariant uses ifName as invariant. As in case of MPLS devices physical and virtual inerface have same ifName, this interface cannot be discovered.

Main future of Cico Device is to discover interfaces, and in this case that main functionality is not available.

Idea priority High
RFE ID 24025
RFE URL
RFE Product Tivoli Netcool Performance Manager
  • Guest
    Reply
    |
    Apr 12, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Operations Management
    Product - Tivoli Netcool Performance Manager

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Operations
    Product - Tivoli Netcool Performance Manager

  • Guest
    Reply
    |
    Oct 11, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Operations
    Product - Tivoli Netcool Performance Manager

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Performance Monitoring
    Product - Tivoli Netcool Performance Manager

  • Guest
    Reply
    |
    Nov 30, 2012

    This RFE is now considered resolved.

    Tom Randles
    TNPM tech pack product manager
    randles@ie.ibm.com

  • Guest
    Reply
    |
    Jul 16, 2012

    IBM provided the current invariant as a working example that pre-dates when Cisco added MPLS interfaces to the ifIndex table. Customers of TNPM often alter our match/discovery formulas to improve/alter invariants, or discovery profiles.
    Note that a product fix to address this will not be possible, due to the disruptive impact such a modification would have on our current installed base for this pack.

    TNPM support have already made recommendations as to how this invariant should be changed in order to discovery these virtual interfaces correctly. These custom modifications do require you to be able to test and validate within your own test environment before deploying in your end-customer’s environment.

    We advise caution in any manipulation of invariant, as changing the invariant can cause the previous instances to be "burned" (removed with prejudice):

    1. Current sub-element will be "burned" which means the su-element that is currently collecting will be completely disabled
    2. The same sub-element will be re-discovered but with a different dbIndex. In other words, there will not be any continuity in charts, between the "new" and "old" sub-elements
    3. The historical data will be still available under the "old" sub-element.

    We continue to recommend our MPLS pack to understand how the data is passed within your environment. We should investigate means by which we can validate this.


    Tom Randles
    TNPM tech pack product manager