Delay processing SNMP requests and sometimes no response at all due to using Unicode strings in Edge name

Products

• VMware VeloCloud SD-WAN

Issue/Introduction

SNMP responses are delayed and sometimes no response at all when peer names contain Unicode strings like "u', Ú, Ë ..etc."

By checking SNMP agent logs, they were running fine and SNMP coming from server is set to ACCEPT but Unicode error logs were observed.

2024-09-17T08:24:32.183 ERROR   [oids (13740:MainThread:13740)] [VCE.Path]<update>: Path failed update buffer: UnicodeEncodeError('ascii', u'ÚË/Âóę/', 16, 17, 'ordinal not in range(128)')

 

Environment

all environments and builds

Cause

The peer name was using Unicode string name, which is not processed by snmpagent.py-veloedge python code. Due to this the rest of the objects waiting to be inserted into the MibTree are NOT inserted and the whole code flow is deemed as “update_failure”.

2024-09-17T08:24:32.183 ERROR   [oids (13740:MainThread:13740)] [VCE.Path]<update>: Path failed update buffer: UnicodeEncodeError('ascii', u'ÚË/Âóę/', 16, 17, 'ordinal not in range(128)')

 

Resolution

Client needs to update Edge names to correct format to not include special characters as: u', Ú, Ë, ..etc.