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.
The tests in the task Check connectivity ANY2ANY between Leaf (galaxy/junos_ping) of the playbook pb.check.underlay.yaml fail when it is cross POD tests.
the spines are configured with an export policy bgp-ipclos-out. The term term as-path doesnt advertise the routes from remote leaves to local leaves (so leaves on POD X doesnt learn the loopback of leaves on POD Y).
Here's the policy (roles/underlay-ebgp/templates/main.conf.j2):
policy-statement bgp-ipclos-out {
term loopback {
from {
protocol direct;
route-filter {{ loopback_ip }}/32 orlonger;
}
then {
{% if underlay.community is defined %}
community add MYCOMMUNITY;
{% endif %}
next-hop self;
accept;
}
}
{% if underlay.community is defined %}
term as-path {
from {
as-path asPathLength2;
community MYCOMMUNITY;
}
then reject;
}
{% endif %}
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.
The tests in the task Check connectivity ANY2ANY between Leaf (galaxy/junos_ping) of the playbook pb.check.underlay.yaml fail when it is cross POD tests.
Ideally we should rewrite this task.
They fail for 2 reasons:
Here's the policy (roles/underlay-ebgp/templates/main.conf.j2):
The text was updated successfully, but these errors were encountered: