Hi,
Sorry, didn’t pay attention to PE-CE protocol…
In this case yes, you seem to be right regarding 1st and 2nd point.
One workaround that I see in this situation is the usage of “conditional advertising”, this way you can attach SOO on CE1 advertised routes to PE1 only if backdoor link exist (the route to the CE2 loopback is in the CE1 routing-table, or indirect static route…), the same should be accomplished on CE2.(Pay attention that CE1 and CE2 loopbacks should not be advertised to PE routers...)
This will solve the problems related to 1st and 2nd point.
On CE1:
[edit]
policy-options {
policy-statement export-to-my-isp {
term a {
from {
protocol direct;
condition CE2-SOO;
}
then {
community add my-soo;
accept;
}
}
term b {
from {
protocol direct;
}
then {
accept;
}
}
}
Condition CE2-SOO {
if-route-exists {
1.1.1.1/32;//CE2 loopback address
table inet.0;
}
}
}
This way if the CE2 loopback won't be in CE1 routing-table, the CE1 prefixes will be advertised to PE without SOO.