04-02-2019 09:08 AM
The issue described in bug report CSCux87714 is now affecting our infrastructure.
The pipe character naming convention, used by ACI when deploying EPGs to VMware as portgroups - may be valid via the VMware API used during the portgroup creation - but invalid later when accessed through the VMware SDK.
This is the situation described in the following Veeam document https://www.veeam.com/kb2074.
The bug report mentions a number of releases as affected by this bug, and later releases as fixed - but what does this mean?
Can the use of the pipe character be overridden in these releases?
The bug report doesn't mention that - just that the known issue is fixed in the later versions.
04-02-2019 01:01 PM - edited 04-02-2019 01:01 PM
Hello,
That means the delimiter character can now be configured:
The acceptable symbols are |, ~, !, @, ^, +, or =.
Remi Astruc
04-02-2019 02:07 PM
That would be perfect, unfortunately for us - all of those characters are on the list that are invalid for the VMware SDK.
04-02-2019 02:45 PM
So now that's a VMware issue ;-)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: