BGP routing rollup, protocol default routing, and key problem validation

A key problem statement

(a) How does the ACL match the same subnet and the different mask routing entries? How do I match the same mask, different entries for subnets?

(ii) Why does a summary route cause the rollover of a BGP neighbor?

(iii) Why does the ACL not match the route entry when using Attribite-map?

(d) How to use Advertise-map,suppress-map,unsuppress-map,attribute-map and Route-map five-way map? Give an example.

(v) The two schemes of route filtering are respectively?

(vi) Two ways in which BGP generates protocol default routes.

Problem one: Use the "standard ACL" matching mask, different subnets, and use "extended ACL" to match the subnet, and the route entries with different masks.

Because the standard ACL only compares the network address portion, the network mask length is not checked, and the extended ACL not only compares the network address portion, but also checks the length of the netmask. The extended ACL here is a special extended ACL whose basic format is:

Access-list Access-list-number {deny | permit} IP Source Source-wildcard source-mask source-mask-wildcard.

Example: Figure

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Network/lyjs/

After the basic configuration is complete, you can check for a total of six OSPF routes on the R2:

Here we use the distribution list distribute-list to manipulate the route on R2: (Tips: Only one distribution list can be configured below a routing process, otherwise the configuration will overwrite previously configured)

1. A. Use standard ACLs to match the same mask, evidence for entries with different subnets:

Distribute-list1 in

Access-list 1 deny 172.16.1.0 0.0.2.255 delete 1.0,3.0 route

Access-list 1 Permit any