Edge may report the wrong interface speed to SNMP ifHighSpeed OID

Products

• VMware
• VMware SD-WAN by VeloCloud

Issue/Introduction

Symptoms:

SNMP poller might see incorrect speeds from  all routed ports on one or multiple SD-WAN Edges

Below example of an edge that is facing the issue(wrong speed is observed)

edge:~# snmpwalk -v2c -c velocloud-comm-ro 127.0.0.1 1.3.6.1.2.1.31.1.1.1
IF-MIB::ifName.16777216 = STRING: GE1   *****
IF-MIB::ifName.16777217 = STRING: GE2   *****
IF-MIB::ifName.16777218 = STRING: SFP1  *****
IF-MIB::ifName.16777219 = STRING: LAN1  *****

IF-MIB::ifHighSpeed.16777216 = Gauge32: 0   *****
IF-MIB::ifHighSpeed.16777217 = Gauge32: 0   *****
IF-MIB::ifHighSpeed.16777218 = Gauge32: 0   *****
IF-MIB::ifHighSpeed.16777219 = Gauge32: 1000   *****

Environment

VMware SD-WAN by VeloCloud
VMware SD-WAN

Cause

This is caused by known issue 111073

The issue is due to "ifHighSpeed" OID not gathering speed information of a dpdk interface from "debug.py --dpdk" command rather than reading from /sys/class/net//speed file that linux provides.

Resolution

This issue is resolved in SD-WAN Edge releases:
Release 4.5.2 (R452-20230628-GA) or later.
Release 5.2.0.0(R5202-20230725-GA) or later

For information on how to upgrade please check the following article: VMware SD-WAN Software Upgrade FAQs

NOTE:- If "ifSpeed" OID cannot accommodate the value of the speed in bps, then it is advised to refer to "ifHighSpeed" OID which gives the value in mbps. This is as per the RFC https://www.rfc-editor.org/rfc/rfc2863.html#section-3.1.7

Additional Information

To be alerted when this article is updated, click Subscribe to Article in the Actions box.