This section describes the commands for configuring and verifying the filter-list.
The filter-list identifies the BGP routes to be filtered by AS_PATH ACL.

The following is an example of configuring BGP route filter with prefix-list. Configure the same conditions with prefix-list as with distribut-list filter.

This section describes the configuration and verification commands for the BGP route filter using prefix-list. The prefix-list identifies BGP routes to be filtered by network address and subnet mask.

This is an example of BGP route filter configuration using distribute-list. BGP routes to be filtered are identified with both standard and extended ACLs.

This section describes the commands for configuring and verifying the BGP route filter using distribute-list. The distribute-list identifies the BGP route information with ACL to be allowed or denied.

It is possible to filter when advertising and receiving route information to and from a specified neighbor with BGP. “How to identify the route information” is important in route filtering with BGP.

The neighbor as-override command rewrites the AS_PATH attribute of a BGP route to advertise to a specific neighbor. This section describes the neighbor as-override command.

The neighbor allowas-in command disables AS_PATH loop prevention for BGP routes received from a specific neighbor.

If the best-path BGP route is not registered in the routing table, the route is placed in RIB Failure status.This section describes RIB Failure of BGP route.

When multiple BGP routes are received for the same network address, the best path (optimal route) is determined and registered in the routing table.
In what order the path attributes of the BGP routes are evaluated to determine the best path is illustrated in detail.