ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Wrong Description and Speed shown for Viptela vEdge interface items in Performance Management


Article ID: 208700


Updated On:


CA Performance Management - Usage and Administration DX NetOps


The Cisco Viptela vEdge devices are discovered via SNMP and their interfaces are being polled. They are discovered against both the standard High Speed Interface Vendor Certification, as well as the Viptela VPN Interface (Port) Vendor Certification. The support for two Vendor Certifications under the same Interface Metric Family is done via Vendor Certification Priority (VCP) Grouping.

When viewing the physical Interface items from the High Speed Interface Vendor Certification in reports the Description and Speed values are not correct.

When viewing the VPN based version of the physical Interface items from the Viptela VPN Interface (Port) Vendor Certification in reports the Description and Speed values are correct.


The values for the interfaces ifDescr and ifSpeed in the standard ifTable and/or ifXTable MIB OIDs do not match values found in the proprietary Cisco Viptela MIB OIDs for InterfaceDesc, interfaceBandwidthDownstream and interfaceBandwidthUpstream. Those are from the Viptela. table(s).

The values seen in Performance Management are correct based on values returned from the device for the target OIDs.


All supported DX NetOps Performance Management releases


The best resolution is resolving the issue on the device causing the two tables values for the same interfaces are matched. That would result in interface items from either Vendor Certification showing the same values in their names.

An alternative is to ensure Reports are set up properly to use the VPN based interface from the Viptela vEdge devices. The recommended one is to use the Viptela VPN Interface (Port) Vendor Certification.

Manage Vendor Certification Priorities documentation

Additional Information

There is no solution for this through Certification changes or customizations. This is because there isn't a way to tie together the interface MIB OID values from the public and private MIB Table OIDs involved.

If a MIB OID value is created on the device that provides a mapping via Index or other value between the tables it could be resolved via Certifications. That would require an Enhancement Request from Cisco.