路由条目控制（Route entry control）.docVIP

路由条目控制（Route entry control） Routing and flow control entry 1, access control list 1), matching is a matching and sequence matching, once out of the access control list 2) and smaller size on the front, behind the large size 3), a deny any implicit 4), delete a fine entry, will delete the entire ACL 5), self generated flow does not match the ACL, only ACL of the flow through my router 6), ACL can match the specific address space, ACL is unable to accurately match the mask 7), the flow control is to control the header information (source address, destination address, source port, destination port, protocol), not the specific user data 8), placed in from near the location, extended from the source is placed in the near position 2, if you want to control the flow, you can use the access control list, if the routing control information to how to do? The application of access control list is unable to effectively control the routing information, routing information is to control the flow, his content is included in the packet. 1) re distribution 2), distance management 3), using the distribution list 4), using PBR routing strategy 3, weight distribution: to achieve mutual notification routing information between two different routing protocols, routing redistribution may lead to routing loops or suboptimal routing. The distribution has a concept of the metric: when the weight distribution, measure the default 1) and distributed into RIP Weight distribution is static or direct, the metric is 1 other protocol default metric 0 (infinite) need to specify the metric manual 2) and distributed into EIGRP If it is static or direct, parameters of the metric parameters for the notification interface default to 0 other protocols need to specify the metric manual 3), distribution OSPF Redistribute static, direct, rip, EIGRP by default only notice main class to add subnets so you can notice the subnet, the default is E2, the metric is 20. If the weight distribution is BGP, the metric