[j-nsp] confederation bgp - path selection

Aaron Gould aaron1 at gvtc.com
Mon Jun 12 15:53:48 EDT 2017


Ahh, and so my next question was going to be, then if it’s path length is 0 then why is it showing an AS in the path list at all ?  65001 is shown… but I just checked another router and I see that the other router that is *not* in the confederation shows an AS with NO parenthesis around the AS path.  Is this significant to confederations where the AS’s are listed in parenthesis but not in normal bgp ?   AS 12345 is not enclosed in parenthesis, but the confed router has AS Path 65001 with parenthesis around it.

 

 

{master:0}

me@ 5048> show route protocol bgp 0.0.0.0 aspath-regex 12345 table one.inet.0

 

one.inet.0: 695 destinations, 1442 routes (695 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

 

0.0.0.0/0          *[BGP/170] 3w3d 10:46:22, MED 2468, localpref 100, from 10.101.0.1

                      AS path: 12345 I, validation-state: unverified

                    > to 10.101.21.5 via ae0.0, Push 16018

 

 

My confederation example….

 

[edit]

r3 at lab-mx104:r3# run show route protocol bgp 192.168.100.0



inet.0: 38 destinations, 41 routes (38 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both



192.168.100.0/24 <http://192.168.100.0/24>    *[BGP/170] 00:51:05, localpref 100, from 10.0.2.6

                      AS path: (65001) I, validation-state: unverified

                    > to 10.0.4.2 via lt-0/1/0.32

                    [BGP/170] 00:50:56, localpref 100, from 10.0.6.1

                      AS path: I, validation-state: unverified

                    > to 10.0.4.14 via lt-0/1/0.31




 

-          Aaron Gould



More information about the juniper-nsp mailing list