SDWAN-Client Windows user tunnels are unstable with error "bad dow name"

Products

• VMware VeloCloud SD-Access

Issue/Introduction

SDWAN-Client Windows user may face the tunnels are unstable. The tunnels gets connected for a few seconds and then gets disconnected.

Below error messages are seen in the user logs.

ananda.log:[2024-09-16 12:16:28.233] [1.35.14] [warning] [policy.cpp:45] Policy allow exception oops: bad dow name: il
ananda.log:[2024-09-16 12:16:29.154] [1.35.14] [warning] [policy.cpp:45] Policy allow exception oops: bad dow name: il
ananda.log:[2024-09-16 12:18:24.422] [1.35.14] [warning] [policy.cpp:45] Policy allow exception oops: bad dow name: il
ananda.log:[2024-09-16 12:18:25.289] [1.35.14] [warning] [policy.cpp:45] Policy allow exception oops: bad dow name: il
ananda.log:[2024-09-16 12:18:50.975] [1.35.14] [warning] [policy.cpp:45] Policy allow exception oops: bad dow name: il

Environment

VMware SDWAN-Client, SD-WAN Client, SD-Access users running on Windows OS

Cause

Windows OS does not provide TimeZone in a usable manner for developers like other OS e.g. Linux, Mac, IOS, and Android
The SDWAN Client software uses a different utility to get the details from Windows OS.

There was a change in the third party utility database on 1st week of September 2024. Because of the change in the format, the SDWAN-Client software with Time Range config in the Context Setting fails to parse the configuration in a correct format. As the context is not parsed properly the context validation fails and this brings down the tunnels.

This is affecting all existing SDWAN-Client versions.

Resolution

Fix:
This issue will be resolved in the upcoming sw version, scheduled to be released in 4th week of September 2024.

Workaround:
Do not use the Time Range in the Context.