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
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
inter POD L2 between severs is not working.
Because of the term as-path in the policy bgp-ipclos-out in all the spines, there is no vxlan tunnels between leaves in pod1 an dleaves in pod2: so, inter POD L2 between severs is not working.
In order to fix this, I had to deactivate this term. Once this term is deactivate, L2 communocation beytween PODs is OK (because leaves has full mesh vtep between them).
I know we need this policy for anothe purpose, but maybe we should rewrite it differently otherwise inter POD is KO.
lab@spine-01> show configuration | compare rollback 1
[edit policy-options policy-statement bgp-ipclos-out]
! inactive: term as-path { ... }
{master:0}
lab@spine-01> show configuration policy-options policy-statement bgp-ipclos-out
term loopback {
from {
protocol direct;
route-filter 100.0.0.11/32 orlonger;
}
then {
community add MYCOMMUNITY;
next-hop self;
accept;
}
}
inactive: term as-path {
from {
as-path asPathLength2;
community MYCOMMUNITY;
}
then reject;
}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
inter POD L2 between severs is not working.
Because of the term as-path in the policy bgp-ipclos-out in all the spines, there is no vxlan tunnels between leaves in pod1 an dleaves in pod2: so, inter POD L2 between severs is not working.
In order to fix this, I had to deactivate this term. Once this term is deactivate, L2 communocation beytween PODs is OK (because leaves has full mesh vtep between them).
I know we need this policy for anothe purpose, but maybe we should rewrite it differently otherwise inter POD is KO.
The text was updated successfully, but these errors were encountered: