Hi
I am looking at this policy hierarchy and wondering why the community attribute is not added to the eBGP routes when I do a show advertising routes detail.
If there is no bgp match in p1 then why is p0 not evaluated, is this because the default export policy is to re-advertise all active BGP routes to all BGP speakers and therefore p0 is never evaluated ? or am i misunderstanding routing policy evaluation a the fact there is a neighbor policy negates totaly the global policy?
instance-type vrf;
vrf-export p0;
protocol bgp {
group external-peers {
type external;
neighbor 192.168.0.1{
export p1;
}
}
}
}
#export policy evaluation order: p1->p0
policy-statement p1 {
term redistribute-ospf {
from protocol [ ospf direct ];
then accept;
}
}
policy-statement p0
term EXPORT {
from protocol [ ospf direct bgp ];
then {
community add CORE_RT;
accept;
}
}
term REJECT_ALL {
then reject;