VNA Viptela interfaces missing device name prefix in Spectrum

Products

• Network Observability

Issue/Introduction

VNA Viptela integration interfaces in Spectrum do not consistently prepend the device name to the interface name.

Environment

• Product: DX NetOps Spectrum before 25.4.4

• Integration: VNA Viptela

Cause

SYMPTOMS:

• Certain SDN_NetworkInterface models display only the interface name (e.g., "GigabitEthernet0/0/3.200") instead of the expected "<DeviceName>_<InterfaceName>" format.

• Attributes ComponentNickName (0x12a1f) and HWComponent Description (0x129e0) point to the old/incorrect interface name.

CONTEXT: This occurs during the update process from the VNA Viptela integration when interface names are modified on the VNA side.

IMPACT: Integration with downstream systems like ServiceNow is impacted due to inconsistent naming conventions.

Resolution

 

1. UPGRADE TO NETOPS 25.4.4

   The fix for this defect is natively included in NetOps release 25.4.4.

   EXPECTED: Upgrading to 25.4.4 resolves the naming inconsistency for VNA-discovered devices and interfaces.

2. VERIFY INTERFACE NAMING

   Discover a VNA device with SDN Router interfaces and modify an interface name on the VNA side.

   EXPECTED: Spectrum updates the name to the modified version while correctly maintaining the <DeviceName>_ prefix.

 

VERIFY SUCCESS:

• Interface names display as <DeviceName>_<InterfaceName> after VNA updates.

• ComponentNickName (0x12a1f) and HWComponent Description (0x129e0) reflect the correct naming.

Additional Information

ROOT CAUSE: Defect DE179243. The code failed to correctly prepend the device name when an interface name update was received from VNA, and incorrectly allowed VNA updates to overwrite SNMP-discovered device names during reconciliation.

RELATED RESOURCES:

• Defect ID: DE179243