HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

r
ramd.conf(4) ramd.conf(4)
both Specifies bgpd to install both less specific and more specific routes.
Route Filtering for BGP
For BGP, you can configure the update filter.
bgpd applies this filter on incoming and outgoing update
messages. There can be many
route_filter configuration statements. If no filter is configured, filter
policies are not applied to the BGP packets.
The syntax of the route_filter configuration statement is as follows:
route_filter filter-name {
[as asnum]
[(prefix prefixlength)|(
hosthost-address)|all]
[
aspath aslist]
dir (in|out);}
(allow|restrict);
where:
as asnum Specifies the remote autonomous system (AS) number based on which
bgpd applies the
filter.
prefix prefixlength Specifies the route prefix based on which
bgpd applies the filter.
host host-address
Specifies the host routes on which bgpd applies this filter.
all Specifies bgpd to filter all routes.
aspath aslist Specifies the AS path list based on which bgpd applies this filter.
dir (in|out) Specifies the direction of update messages on which
bgpd applies this filter. The in
option applies the filter on incoming routes and the out option applies the filter on out-
going routes.
allow|restrict;
Specifies to allow or restrict the incoming or outgoing routes. By default, bgpd allows
all routes.
Route Aggregation for BGP
Route aggregation is the process of merging two or more routes to form a single route on the basis of
matching bits in each route. It reduces the number of routes in the BGP route update message. The
receiving BGP neighbor router installs the aggregate route in the kernel routing table. Hence, route aggre-
gation reduces the number of routes in the kernel routing table.
bgpd that generates aggregate routes do
not use the originated aggregate routes for packet forwarding.
The aggregate configuration statement can be used to generate aggregate routes. If the aggregate
configuration statement is not specified in the configuration file, bgpd
does not perform route aggregation.
Route aggregation is effective only when the
overlap both configuration statement is specified.
The syntax of the aggregate configuration statement is as follows:
aggregate {
[prefix prefixlength
[all|summary-only ]
[preference preference-value]
[restrict]];
};
where:
prefix prefixlength Specifies the routes that can be aggregated and its prefix length.
all|summary-only
Specifies bgpd to advertise aggregated routes and more specific routes or advertise only
aggregated routes.
preference preference-value
Specifies the preference for the aggregated routes. By default, this value is 130.
restrict Specifies that bgpd must not aggregate with this route.
352 Hewlett-Packard Company − 14 − HP-UX 11i Version 3: February 2007