Routing

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 {
                       }
                }

Hi,

Try this as well:

policy-statement STATIC_ROUTE

term export_static{

from protocol static;

then accept;

Then export in into your BGP.

Hi,

Oh sorry, I want to verify if you want to export static routes into your BGP?

Yes, I want to export the static routes to advertise to the neighbor. I think your first response will work, but I would like to know if the config in my example would work.

Hi,

Okay, why you want to use community string on exporting static routes into your BGP?

In my opinion you may just explicitly configure the policy that contains exporting static route protocol.

You add community values for management purposes, for tracking, logging, for use in routing policies..all kinds of reasons. Usually used internally within an AS. 

Hello barbijo

You can run this command 

>show route advertising-protocol bgp 10.10.10.10

And that will will show you the routes being advertised. You can test this with your policy. I am not sure if your config alone will work. You may want to also add this to your term: "set term COMMUNITY_ACCEPT from protocol static"