Device Interface & its sub-interface misnamed in CA Performance Management (CAPM)
search cancel

Device Interface & its sub-interface misnamed in CA Performance Management (CAPM)

book

Article ID: 242139

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps CA Infrastructure Management

Issue/Introduction

Devices discovered in Spectrum show the interfaces with the correct names, however, in CAPM, some interfaces and sub interfaces' names are not correct. Rediscovery/update metric families for the Interface MF makes no difference. How can the interface names be corrected?

Environment

DX NetOps CAPM Release : 21.2

Cause

This is a case of a "not present" (or retired) interface being synced to CAPC from the DA.

Two interfaces with the same ifindex and parent device and same SourceID (either DA or NFA).

Resolution

From the mysql DB on the CAPC server, you would first have to identify all the interfaces with duplicate itemIDs using:

select itemID, count(*) n from dst_interface group by itemID having n > 1;

The above query will return all interface items with duplicate ItemIDs and tell you how many duplicates there are (count c). So for example, you may see output such as:

mysql> select itemid, count(*) c from dst_interface group by itemid having c > 1;

+--------+---+

| itemid | c |

+--------+---+

|  56693 | 2 |

|  57868 | 2 |

|  59082 | 2 |

|  59084 | 2 |

|  59085 | 2 |

|  59086 | 2 |

|  60423 | 2 |

|  67819 | 2 |

|  67820 | 2 |

|  67821 | 2 |

|  68650 | 2 |

|  70438 | 2 |

|  70439 | 2 |

|  70440 | 2 |

|  70441 | 2 |

|  70442 | 2 |

|  70443 | 2 |

|  70444 | 2 |

Then, you would have to search for the LocalID and name for each of the ItemIDs returned from above using:

select localid, itemname, itemdesc, ifindex from dst_interface where itemid=<itemID>

This will return the localID and other fields such as item name, description & Index. For example:

mysql> select localid, itemname, itemdesc, ifindex from dst_interface where itemid=56693;

+-----------+----------------------------------------+----------------------------------------+---------+

| localid   | itemname                               | itemdesc                               | ifindex |

+-----------+----------------------------------------+----------------------------------------+---------+

| 0x1000c42 | Sim36527:CsrBrtge01.net.com_fxp0       | Sim36527:CsrBrtge01.net.com_fxp0       |       1 |

| 80276     | GE0/0/0                                | GE0/0/0                                |       1 |

+-----------+----------------------------------------+----------------------------------------+---------+

2 rows in set (0.00 sec)

You can then check the LocalIDs returned to see if any have been retired using the REST query:

DA:8581/rest/retired/<localID>

And see what comes back with a response. That's the "Not Present" item.

Then use same URL:

DA:8581/rest/retired/<localID>

with a DELETE REST action to remove that "Not Present" interface from the DA and when it syncs the delete, you should be able to see the correct interface name/etc in t_interface table and the CAPC UI.