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

r
ramd.conf(4) ramd.conf(4)
Using ram_monitor for BGP
ram_monitor can be used to monitor the BGP daemon. The BGP section in the RAMD configuration file
provides a directive to specify the CLI port number.
cliport port-number;
bgpd
listens for ram_monitor connection on port-number. If the CLI port number is not specified,
bgpd does not provide CLI service.
Maximum Routes for BGP
The maxroutes statement configures the maximum routes that
bgpd can store in its routing table.
The syntax of the
maxroutes configuration statement is as follows:
maxroutes numb-of-routes
;
where numb-of-routes specifies the maximum routes that
bgpd can store in its routing table. By default,
this value is 5000.
Maximum Peers for BGP
The maxpeers statement configures the maximum peers that
bgpd supports.
The syntax of the maxpeers configuration statement is as follows:
maxpeers numb-of-peers;
where numb-of-peers pecifies the maximum peers that
bgpd supports. By default, this value is 50.
Enabling Synchronization for BGP
The synchronization rule of BGP states that if an Autonomous System (AS), such as AS 1, passes traffic
from one AS to another, BGP does not advertise a route before all routers within the AS (AS 1) have
learned about the routes through an Interior Gateway Protocol (IGP). The BGP section in the RAMD
configuration enables or disables synchronization of routes with IGP.
The syntax of the
sync configuration statement is as follows:
sync (on|off);
where:
on Enables bgpd synchronization.
off Disables bgpd synchronization. By default, synchronization is disabled.
Propagation of Non-BGP Routes
The propnon-bgp statement specify the control or propagation of non-bgp routes to external peer or both
external and internal peers. By default, bgpd propagates non-bgp routes to both external and internal
peers.
The syntax of the propnon-bgp configuration statement is as follows:
propnon-bgp (external|both);
where:
external Specifies propagation of non-bgp routes to external peers.
both Specifies propagation of non-bgp routes to both external and internal peers.
Overlapping Routes for BGP
The overlap statement sets policy handling of overlapping routes. Route overlap occurs when bgpd
receives a set of less and more specific routes.
The syntax of the overlap configuration statement is as follows:
overlap (less|more|both);
where:
less Specifies bgpd to install the less specific routes.
more Specifies bgpd to install the more specific routes.
HP-UX 11i Version 3: February 2007 − 13 − Hewlett-Packard Company 351