HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
g
gated.conf(4) gated.conf(4)
the section on Route Filtering.
peer host
A peer clause configures an individual peer. Each peer inherits all parameters specified on a
group as defaults. Those default may be overridden by parameters explicitly specified on the
peer subclause.
Within each group clause, individual peers can be specified or a group of potential peers can be specified
using allow. Allow is used to specify a set of address masks. If GateD receives a BGP connection request
from any address in the set specified, it will accept it and set up a peer relationship.
Peer parameters
The BGP peer subclause allows the following parameters, which can also be specified on the group
clause. All are optional.
metricout metric
If specified, this metric is used as the primary metric on all routes sent to the specified peer(s).
This metric overrides the default metric, a metric specified on the group and any metric specified
by export policy.
localas autonomous_system
Identifies the autonomous system which GateD is representing to this group of peers.. The
default is that which has been set globally in the autonomoussystem statement.
nogendefault
Prevents GateD from generating a default route when EGP receives a valid update from its
neighbor. The default route is only generated when the gendefault option is enabled.
gateway gateway
If a network is not shared with a peer, gateway specifies a router on an attached network to be
used as the next hop router for routes received from this neighbor. This parameter is not needed
in most cases.
preference preference
Specifies the preference used for routes learned from these peers. This can differ from the
default BGP preference set in the bgp statement, so that GateD can prefer routes from one
peer, or group of peer, over others. This preference may be explicitly overridden by import pol-
icy.
preference2 preference
In the case of a preference tie, the second preference, preference2 may be used to break
the tie. The default value is 0.
lcladdr local_address
Specifies the address to be used on the local end of the TCP connection with the peer. For exter-
nal peers the local address must be on an interface which is shared with the peer or with the
gateway of the peer when the gateway parameter is used. A session with an external peer will
only be opened when an interface with the appropriate local address (through which the peer or
gateway address is directly reachable) is operating. For other types of peers, a peer session will
be maintained when any interface with the specified local address is operating. In either case
incoming connections will only be recognized as matching a configured peer if they are addressed
to the configured local address.
holdtime time
Specifies the BGP holdtime value to use when negotiating the connection with this peer, in
seconds. According to BGP, if GateD does not receive a keepalive, update, or notification mes-
sage within the period specified in the Hold Time field of the BGP Open message, then the BGP
connection will be closed. The value must be either 0 (no keepalives will be sent) or at least 3.
version version
Specifies the version of the BGP protocol to use with this peer. If not specified, the highest sup-
ported version is used first and version negotiation is attempted. If it is specified, only the
specified version will be offered during negotiation. Currently supported version are 2, 3 and 4.
passive
Specifies that active OPENs to this peer should not be attempted. GateD should wait for the peer
to issue an open. By default all explicitly configured peers are active, they periodically send
OPEN messages until the peer responds.
Section 4−−100 − 29 − HP-UX Release 11i: December 2000
___
___