Specifications

bgp set peer-group
108 SSR Command Line Interface Reference Manual
the peer to issue an OPEN. By default, all explicitly configured peers are active, they
periodically send OPEN messages until the peer responds. Note that if it is applied to
both sides of a peering session, it will prevent the session from ever being established.
send-buffer <num>
Controls the amount of send buffer acquired from the memory subsystem. The
maximum supported is 65535 bytes. By default, BGP acquires the maximum
supported. Specify a number from 4096 – 65535.
recv-buffer <num>
Controls the amount of receive buffer acquired from the memory subsystem. The
maximum supported is 65535 bytes. By default, BGP acquires the maximum
supported. Specify a number from 4096 – 65535.
in-delay <num>
Used to dampen route fluctuations. In delay specifies the amount of time in secs a
route learned from a BGP peer must be stable before it is accepted into the routing
database. Specify a number equal to or greater than 0. The default value is 0, meaning
that this feature is disabled.
out-delay <num>
Used to dampen route fluctuations. Out delay is the amount of time in secs a route
must be present in the routing table before it is exported to BGP. Specify a number
equal to or greater than 0. The default value is 0, meaning that this feature is disabled.
keep all|none
Used to retain routes learned from a peer even if the routes' AS paths contain one of
our exported AS numbers.
show-warnings
This option causes GateD to issue warning messages when receiving questionable
BGP updates such as duplicate routes and/or deletions of non-existing routes.
Normally these events are silently ignored.
no-aggregator-id
This option causes GateD to specify the router ID in the aggregator attribute as zero
(instead of its router ID) in order to prevent different routers in an AS from creating
aggregate routes with different AS paths.
keep-alives-always
This option causes GateD to always send keepalives, even when an update could
have correctly substituted for one. This allows interoperability with routers that do
not completely obey the protocol specifications on this point.
v3-asloop-okay
By default GateD will not advertise routes whose AS path is looped (i.e. with an AS
appearing more than once in the path) to version 3 external peers. Setting this flag
removes this constraint. Ignored when set on internal groups or peers.