Added validation check for CSCwt58626#405
Conversation
lovkeshsharma702
left a comment
There was a problem hiding this comment.
all intigrated test passed.
|
|
||
| Due to [CSCwt58626][77], when targeting APIC version 6.1(3f) to 6.1(5e) or 6.2(1g) , if the InfraVLAN overlaps with any user-configured VLAN pool range in Access Policies, fault `F4701` is raised for VLAN pools that include the InfraVLAN. After the upgrade, domains linked to those VLAN pools cannot be associated with new EPGs, although existing EPGs continue to function. | ||
|
|
||
| To avoid this issue, modify user VLAN pool ranges so that the InfraVLAN does not overlap with any configured block or select target version with fix. |
There was a problem hiding this comment.
@lovkeshsharma702 include some detail about the planned fix, otherwise this checks details will have to be updated again after release.
There was a problem hiding this comment.
@lovkeshsharma702 include some detail about the planned fix, otherwise this checks details will have to be updated again after release.
@monrog2 this was a regression in 6.1(3f) to 6.1(5e) or 6.2(1g). fixed above 615 and 6.2.x. only 6.2.2eis release so far, hence fix version for 615 not mentioned in the bug. @muthu-ku please add 6.2.2e as fixed version in bug.
There was a problem hiding this comment.
Main point of this one is to call out the behavior change implemented in the fixed versions.
my understanding is:
PD will block path binding on user tenant if the binding it pushing the infra VLAN.
HOWEVER, Infra tenant can do this without issue.
affected version behavior relies solely on access policy lookup, which means whether infra or user tenant, any extension of infra VLAN causes the fault + blocking condition seen today.
point for clarification is how this would affected vmm bindings for infra vlan within user tenant, such as k8 integration
Added new validation for the defect CSCwt58626.
This check will check if the InfraVLAN overlaps with any user-configured VLAN pool range in Access Policies.
Apic failure logs:
apic_failure_log.txt
apic_full_run_log.txt
pytest_full_run_log.txt
pytest_log.txt