I would just like to know if tagging static route with the community string below would be enough to insert into the export routing policy to advertise to BACKBONE? Assuming that the LOCAL_ROUTE_POLICY policy accepts the 100:4001community
policy-statement LOCAL_ROUTE_POLICY
term COMMUNITY_ACCEPT {
from community INTERNAL;
then accept;
}
community INTERNAL members 100:4001;
NetworkA {
instance-type virtual-router;
routing-options {
static {
route 10.208.75.132/32 {
qualified-next-hop 10.208.75.140 {
interface irb.2423;
}
community 100:4001;
}
router-id 10.0.0.1;
autonomous-system 100;
}
protocols {
bgp {
group BACKBONE {
type external;
import ROUTE_POLICY;
family inet {
unicast;
}
export LOCAL_ROUTE_POLICY;
peer-as 220;
neighbor 10.10.10.10 {
}
}