IPv6 Addresses in Virtual Service Application Logs are not in human-readable format on Remote Syslog Servers

Products

• VMware Avi Load Balancer

Issue/Introduction

• This issue occurs when utilizing remote syslog servers to collect application logs from Virtual Services configured with IPv6 addresses.
• Customers may observe that the IPv6 addresses within these logs are not displayed in a human-readable format, instead, they appear as a series of unintelligible characters (e.g., \u0005\u000e \u0000\u0001\u0011i\u0006)
• This issue hinders log analysis and troubleshooting efforts related to IPv6 traffic.

Environment

This issue affects environments where:

• Virtual Services are configured with IPv6 addresses.
• Application logs are streamed from the Service Engine (SE) to a remote syslog server.
• The remote syslog server is receiving logs from Service Engines.

 

 

Cause

• The root cause of this issue was identified as a formatting problem within the Service Engine's logging mechanism when processing and streaming IPv6 addresses in application logs. The underlying system was not correctly converting the IPv6 address format into a standard, human-readable string before transmission to the remote syslog server.
• This resulted in the addresses being encoded in an uninterpretable binary or non-standard format upon receipt.

Resolution

Please upgrade or patch the system to the fix version.

AV-235927: In external streaming logs, the IPv6 values are not in a human-readable format
Fix Version(s): 31.2.1, 30.2.4, 22.1.7-2p7, 31.1.1-2p3, 30.2.3-2p2 

This resolution ensures that IPv6 addresses within application logs streamed from the Service Engine are correctly formatted and appear in a human-readable format on the remote syslog server.