rstp ccnp

rstp ccnp

! ! Automatic generation Configuration example 1 : as-path access-list with filter-list 200 i Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Set interface priority, CISCO IOS default 128 ; CatOS default 32 100 Origin IGP, metric 0, localpref 100, valid, internal, best Originator: 1.1.1.1, Cluster list: 2.2.2.2 Adding redundant routing The Permit/deny keyword has a different role in different deployment scenarios. After the summary command is added with the as-set keyword, the generated summary route can inherit some path attributes of the detailed route, thus avoiding some problems. The rules for inheriting detail attributes from as-set are as follows: Ip prefix-list 100 permit 100.100.100.0/24 route-map COST1 permit 10 When a BGP router sends a route update to its EBGP neighbor, it cannot carry the LP attribute. The LP value of the EBGP route received by the other party is null (even the LP field is there), but it will assign a default to this route locally. Value, that is Neighbor 10.1.25.5 remote-as 345 no auto-summary ! ! Automatic generation You can not route the network , but the origin of the route,rstp ccnp, configure a summary static, and then network the summary route, this method is not recommended. On Demand stub Routes Ok, then let's start the experiment below: BGP metric is set to IGP metric S The so-called seed metric refers to when I use a route to re-publish from an external routing protocol to this routing protocol, if the metric of the route is not manually specified , the default metric is used . Look at the following table (the following table is a recognized default value that can be modified using the default-metric in the routing process ): Default route 108 R3 , R4 , and R5 run OSPF , announcing the three interconnect interfaces and their respective LOOPBACKs. Show tcp bri Neighbor FastEthernet0/0 Notifacation packets , resulting in session is interrupted; it can be re- AS on the border router IN strategic direction. Interface fast0/24 Ip dhcp snooping Field name neighbor RC-ip the EBGP Multihop- 2 // jump between them number 2 Redistribute connected subnets redistribute rip metric 10 subnets 4 Repeat, you can configure multiple The description of several fields ( ISL header) in the above figure is as follows: Originator: 1.1.1.1, Cluster list: 4.4.4.4, 3.3.3.3 After " 10.1.20.0 " is passed to R2 , since the updated subnet is consistent with the R2 interface main network, R2 receives the update, and uses the interface mask /23 as the mask of the received RIP subnet, then R2 local loading This RIP route is 10.1.20.0/23 . In fact, the prefix length of the route is wrong. We can configure a secondary address on the R2 interface. In this way, RIP will use the mask of the secondary address (if configured) to receive the route. For example, configure R2 with 10.1.123.222/24 .