Applying the Policy Statement on CE Router A

Apply the export-to-my-isp policy statement as an export policy to the EBGP peering on the CE Router A as follows:

[edit]

protocols {

    bgp {

        group my_isp {

            export export-to-my-isp

        }

    }

}

When you issue the show route receive-protocol bgp detail command, you should see the following routes originated from PE Router B with soo community :

user@host> show route receive-protocol bgp 10.12.99.2 detail

inet.0: 16 destinations, 16 routes (15 active, 0 holddown, 1 hidden)

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

vpn_blue.inet.0: 8 destinations, 10 routes (8 active, 0 holddown, 0 hidden)

* 10.12.33.0/30 (2 entries, 1 announced)

     Nexthop: 10.12.99.2

     AS path: 100 I

     Communities: origin:100:1

  10.12.99.0/30 (2 entries, 1 announced)

     Nexthop: 10.12.99.2

     AS path: 100 I

     Communities: origin:100:1

* 10.255.71.177/32 (1 entry, 1 announced)

     Nexthop: 10.12.99.2

     AS path: 100 I

     Communities: origin:100:1

* 192.168.64.0/21 (1 entry, 1 announced)

     Nexthop: 10.12.99.2

     AS path: 100 I

     Communities: origin:100:1

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)

bgp.l3vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 

hidden)