You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(use upvote 👍 for attentions) Describe the bug
When there are three (or more) domains associated to an EPG, the overlapping VLAN pool check may flag it as FAIL - OUTAGE WARNING!! or MANUAL CHECK REQUIRED incorrectly.
Script output
Example:
EPG 1 (VLAN 10)
+--- Domain 1 --> VLAN Pool A (VLAN 10-20)
+--- Domain 2 --> VLAN Pool A (VLAN 10-20)
+--- Domain 3 --> VLAN Pool B (VLAN 15-20)
As shown in the example above, three domains (Domain 1, 2 and 3) are associated to EPG 1 which is using VLAN 10. Domain 1 and 2 are using the same VLAN Pool A while Domain 3 is using VLAN Pool B.
In this case, there are overlapping VLAN IDs (15-20) between these domains, in other words between VLAN Pool A and B. However, the VLAN used for this EPG is 10 which is only in VLAN Pool A, which is used by Domain 1 and 2.
To Reproduce
Described above
Expected behavior
checking the identity of VLAN Pools behind the domains.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
(use upvote 👍 for attentions)
Describe the bug
When there are three (or more) domains associated to an EPG, the overlapping VLAN pool check may flag it as FAIL - OUTAGE WARNING!! or MANUAL CHECK REQUIRED incorrectly.
Script output
Example:
+--- Domain 1 --> VLAN Pool A (VLAN 10-20)
+--- Domain 2 --> VLAN Pool A (VLAN 10-20)
+--- Domain 3 --> VLAN Pool B (VLAN 15-20)
As shown in the example above, three domains (Domain 1, 2 and 3) are associated to EPG 1 which is using VLAN 10. Domain 1 and 2 are using the same VLAN Pool A while Domain 3 is using VLAN Pool B.
In this case, there are overlapping VLAN IDs (15-20) between these domains, in other words between VLAN Pool A and B. However, the VLAN used for this EPG is 10 which is only in VLAN Pool A, which is used by Domain 1 and 2.
To Reproduce
Described above
Expected behavior
checking the identity of VLAN Pools behind the domains.
Additional context
N/A
The text was updated successfully, but these errors were encountered: