Interface aliasname (ifAlias) missing in OData response - DX NetOps Performance Management
search cancel

Interface aliasname (ifAlias) missing in OData response - DX NetOps Performance Management

book

Article ID: 450025

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

Users of DX NetOps Performance Management may observe that OData API responses do not contain the aliasname (ifAlias) for certain SNMP-polled interfaces, even when the device correctly reports these values via snmpwalk and the user has administrative privileges.

Symptoms:

  • OData query results show null or missing values for the aliasname field.
  • The issue affects interfaces classified as "combination items" (physical port and virtual interface).
  • snmpwalk confirms the device provides the ifAlias (OID .1.3.6.1.2.1.31.1.1.1.18).

Cause

The Data Aggregator reuses a single local Item ID for both the physical Port and the Virtual Interface. The DA internal schema only supports one AlternateName attribute per local Item ID. If the names are not synchronized in the Portal, the OData query fails to retrieve the value for the combined item.

Resolution

This issue is a known product limitation.

  • Defect ID: DE165549
  • Status: Targeted to be fixed in a future release.

To be notified of updates to this issue, subscribe to this article by following the steps in KB 275360.

Workaround:

  1. Identify the affected interfaces in the DX NetOps Portal.
  2. Manually update the AlternateName for both the physical port and the virtual interface sharing the same DA local ID.
  3. Ensure the names match exactly.
  4. Verify the OData response using the OData 4 endpoint: http://####:8181/pc/odata4/api/interfaces

If the issue persists, verify the mapping in the database:

sql
 
SELECT * FROM ehealth.item WHERE item_id = ####;