9tut ccnp route lab

9tut ccnp route lab

300, ( aggregated by 300 3.3.3.3 ) // a summary route generated from AS300 , a BGP router 3.3.3.3 produced The switch sends data frames according to the discovered outbound interface. Remove 100 Use decimal. RFC format is 12 : 10000 , hexadecimal is 0x 000C2710 , and then converted to decimal 796432 This summary route generated locally is 172.16.0.0/16 , NH=0.0.0.0 , weight= default value 32768 , origin=i . The detail route is marked as " s " and is therefore suppressed. 200 i Paths: (1 available, best #1, table Default-IP-Routing-Table) Flag: 0x820 Set ip next-hop verify-availability 10.1.1.2 10 track 1 R1 update source IP match, although the update source of R2 configuration is the default (packet outbound interface IP 10.1.12.2 ), but the BGP connection establishment between the two is no problem, because the connection of R1 to R2 is no problem. . At the same time, it is also possible to delve into the routing problem. For example,9tut ccnp route lab, if R2 is localized to the 1.1.1.0 static route and is configured as the default route, we will find that the BGP connection can still be established, because R2 is the passive of the BGP connection in this example. who, R1 have specific routes to initiate connection. However, if the static static route from R1 to 2.2.2.0 is changed to the default, then it will not work, and R1 will consider " no route to peer ".