NAME
bgpd — BGP routing daemon for IPv6
SYNOPSIS
/usr/sbin/bgpd
[-C | -c]
[-f
config_file]
[-N]
[-n]
[-q]
[-t
trace_options]
[trace_file]
DESCRIPTION
bgpd
is a routing daemon that works with Route Administration Manager (RAMD)
for IPv6.
This routing daemon is an implementation of Border Gateway Protocol
(BGP) for IPv6.
bgpd
is invoked automatically if it is enabled in the
/etc/ramd.conf
configuration file.
BGP exchanges information across the Autonomous System (AS) and uses the
path-vector algorithm to select the best path.
It conforms to
IETF RFC 1771,
RFC 2545
RFC 2858,
and
RFC 3392.
This release supports only IPv6 route exchange.
Options
bgpd
supports the following command-line options:
- -C | -c
Parses the configuration file for syntax errors
and terminates
bgpd.
bgpd
exits with status 0 if the configuration file
contains no error.
In case of any error,
bgpd
exits with a non-zero value.
bgpd
prints the configuration file errors, if any, to
the standard output.
-C
and
-c
perform the same function.
- -f config_file
Specifies an alternate configuration file to be used by
bgpd.
By default,
bgpd
uses the
/etc/ramd.conf
configuration file.
- -N
Specifies that
bgpd
runs as a normal process and not as a
daemon.
- -n
Specifies that
bgpd
does not modify the kernel forwarding table.
That is,
bgpd
must not send route updates to
ramd.
- -q
Suppresses
stderr
messages of
bgpd.
Using this option, informational messages that are printed to the
standard output can be suppressed and error messages can be logged using
syslogd(1M).
By default,
bgpd
logs the syslog errors to
/var/adm/syslog/syslog.log.
- -t trace_options
Specifies a comma-separated list of trace options that must be enabled
during startup of
bgpd.
No space is allowed between this option and its arguments.
See
ramd.conf(4)
for information on valid trace options and tracing.
- trace_file
Name of the file used by
bgpd
to log tracing information.
If trace options are specified without specifying a trace file,
bgpd
uses the default trace file
/var/tmp/bgpd/bgpd.log.
Signal Processing
The following signals can be used to control
bgpd:
- SIGHUP
Specifies
bgpd
to reread the configuration file.
bgpd
reads the configuration file and reconfigures its policies.
- SIGINT
Specifies that the current state of
bgpd
is written to
/var/tmp/bgpd/bgpd.dump.
- SIGTERM
Graceful shutdown.
On receipt of
SIGTERM,
bgpd
attempts a graceful shutdown.
All protocol routes are removed from the kernel's
routing table on receipt of
SIGTERM.
- SIGUSR1
Toggle tracing.
If the tracing is currently enabled, this signal suspends
tracing and closes trace file.
If tracing is currently
disabled, the trace file will be reopened and tracing
initiated.
This is used to move trace files.
It is not possible to use
SIGUSR1
if tracing is not
enabled in the configuration file.
AUTHOR
bgpd
was developed by Future software Ltd.
SEE ALSO
netstat(1),
ifconfig(1M),
ram_monitor(1M),
ramd(1M),
rdc(1M),
fork(2),
ramd.conf(4).
- RFC 1246
Experience with the OSPF Protocol
- RFC 1253
OSPF Version 2 Management Information Base
- RFC 1256
ICMP Router Discovery Messages
- RFC 1265
BGP Protocol Analysis
- RFC 1266
Experience with the BGP Protocol
- RFC 1267
A Border Gateway Protocol 3 (BGP-3)
- RFC 1268
Application of the Border Gateway Protocol in the Internet
- RFC 1269
Definitions of Managed Objects for the Border Gateway Protocol (Version 3).
- RFC 1321
The MD5 Message-Digest Algorithm
- RFC 1370
Internet Architecture Board Applicability Statement for OSPF
- RFC 1388
RIP Version 2 Carrying Additional Information
- RFC 1397
Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway
Protocol
- RFC 1403
BGP OSPF Interaction
- RFC 1583
OSPF Version 2.
Printable version
