NAME
rdc — user interface for Routing Administration Manager (RAMD)
SYNOPSIS
/usr/bin/rdc
[-c
coresize]
[-f
filesize]
[-n]
[-q]
[-t
seconds]
{start}
/usr/bin/rdc
( stop | restart |
running )
( ram | ripng | bgp
| isis | all )
/usr/bin/rdc
( dump | coredump )
( ram | ripng | bgp
| isis | all )
/usr/bin/rdc
( kill | term | reconfig
| toggletrace )
( ram | ripng | bgp
| isis | all )
/usr/bin/rdc
( checkconf | checknew | newconf
| modeconf | createconf )
/usr/bin/rdc
( backout | BACKOUT )
/usr/bin/rdc
interface
{ ram }
DESCRIPTION
rdc
provides a user-oriented interface for working with the
ramd
and routing daemons.
ripngd,
bgpd
and
isisd
are referred to as routing daemons.
rdc
provides a command-line interface to start and stop these daemons.
In addition, it provides commands to check the configuration
file for syntax errors, make the daemon dump core,
and dump the current state of the daemon.
rdc
can reliably determine the running state of the routing protocols.
This can be used in shell scripts to manipulate
ramd.
Options
rdc
supports the following command-line options:
- -n
Specifies that
rdc
does not change the kernel forwarding table while running
ramd
and routing daemons.
This option is useful to test the daemons, when the
daemons should operate as a route server that does not forward.
- -q
Suppresses the stderr messages of
ramd
and routing daemons.
This option can be used to suppress informational messages
that are normally printed to the standard output,
and the log error messages through
syslogd(1M).
- -t seconds
Specifies the time in seconds for which
rdc
waits to start, stop, reconfigure and terminate daemons.
By default, this value is set to 10 seconds.
- -c coresize
Specifies the maximum size of a core dump
produced by the routing daemons invoked using
rdc.
- -f filesize
Specifies the maximum size of a file produced
or created by the routing daemons invoked using
rdc.
Commands
The following commands are used to send HP-UX signals to
ramd
or routing daemons for various purposes:
- coredump
Sends an abort signal to the requested daemon and
terminates the daemon with a core dump.
The core files
are generated in the file
/var/tmp/*/core,
where
*
can be
ramd,
ripngd,
bgpd
or
isisd.
- dump
Sends a signal to the requested daemon to dump its current
state into the
/var/tmp/*/*.dump,
where
*
is one of the routing daemons.
- kill
Kills the daemon abruptly.
This command is used when the daemon hangs.
- reconfig
Sends
SIGHUP
signal to the requested daemon to reread
its configuration file and reconfigure its current state.
- term
Sends
SIGTERM
signal to the requested daemon to terminate
gracefully.
- toggletrace
Sends
SIGUSR1
signal to the daemon to toggle the trace.
If tracing is enabled, this command causes tracing to be suspended
and the trace file to be closed.
If tracing is disabled, the trace file is reopened and tracing initiated.
This is useful to move the trace files.
If
ramd
or the routing daemon tracing is modified using this command and the
daemons are reconfigured with the trace options,
the effect on tracing is with respect to the configuration file.
- interface
Sends
SIGUSR2
signal to
ramd
to recheck the interface configuration.
ramd
periodically checks the kernel interface configuration
for any changes.
This command can be used to force
the daemon to check the interface status immediately.
Currently, the only valid argument for this command is
ram,
for checking on
ramd.
By default,
ramd
obtains its configuration information from the
/etc/ramd.conf
file.
rdc
maintains many versions of the configuration file.
The versions of the configuration file maintained by
rdc
are as follows:
- /etc/ramd.conf.new
createconf
command of
rdc
is used to create this configuration file.
- /etc/ramd.conf.prev
When
rdc
must install a new configuration file using the
createconf
command, the existing
/etc/ramd.conf
file is renamed as
/etc/ramd.conf.prev
file.
- /etc/ramd.conf.prev.old
When
rdc
creates a new configuration file, using the
createconf
command, the existing
/etc/ramd.conf,
file is renamed as
/etc/ramd.conf.prev
and the existing
/etc/ramd.conf.prev
is renamed as
/etc/ramd.conf.prev.old
file.
Configuration File Commands
The following commands perform operations related to
configuration files:
- checkconf
Checks
/etc/ramd.conf
for syntax errors.
This is done after changes are made
to the configuration file and before reconfiguring the routing
daemons.
The system administrator use this command to ensure
that there are no syntax errors in the configuration file, which can
otherwise terminate the daemons on reconfiguration.
- checknew
Checks the
/etc/ramd.conf.new
file for syntax errors.
- newconf
Renames the
/etc/ramd.conf.new
file to
/etc/ramd.conf,
retaining the older versions of the configuration files.
This operation fails if
/etc/ramd.conf.new
does not exist.
- backout
Replaces the old configuration file
/etc/ramd.conf.old
to
/etc/ramd.conf.
This command fails, if the
/etc/ramd.conf.old
file does not exist or if the file
/etc/ramd.conf.old
is of zero length, or if the backout command deletes an existing,
non-zero length
/etc/ramd.conf.new
file.
- BACKOUT
Performs a
backout
operation even if the
/etc/ramd.conf.new
file exists and is of non-zero length.
- modeconf
Sets all configuration files to mode 664, owner root and
group trusted non-root user.
This allows a trusted non-root user to modify the configuration files.
- createconf
Creates a new configuration file,
/etc/ramd.conf.new
with zero length.
The file mode is set to 664, owner root and
group trusted non-root user.
This allows a trusted non-root
user to install a new configuration file.
Controlling Daemons
The following commands can be used to control the daemons:
- start
Starts
ramd.
The command returns an error if
ramd
is already running.
It invokes
ramd
and waits for the time period specified with
-t
option.
A non-zero exit status is returned, if an error is
detected while executing the binary, or if a lock is
not obtained on the pid file within the specified wait
time.
Starting
ramd
invokes all the configured protocols in the configuration file
of
ramd.
The following commands can be used to determine the current
state of the daemon or to stop or restart
ramd
and other IPv6 routing protocols.
- running
Determines if daemons are currently running.
rdc
exits with a zero status if the daemon is running and
with a non-zero value if the daemons are not running.
- stop
Stops the requested routing daemon gracefully.
Stopping
ramd
stops all the daemons.
- restart
Restarts the requested daemon.
rdc
reports an error, if there is a failure.
EXAMPLES
To start
ramd,
type the following at the HP-UX command prompt:
If successful, the pid of the
ramd
daemon is displayed.
To get the current state of the daemons, type the following at
command prompt:
This will dump the current state of the
ramd
and routing daemons.
The dump files for the
ramd
and routing daemons are
/var/tmp/ramd/ramd.dump
and
/var/tmp/*/*.dump,
respectively; where
*
is one of the routing daemons.
To reconfigure the routing daemons, change the configuration file
/etc/ramd.conf
and issue the following command at the command prompt:
/usr/bin/rdc reconfig (ram|bgp|isis|ripng)
AUTHOR
rdc
was developed by Future software Ltd.
FILES
/usr/sbin/ramd
/usr/sbin/ripngd
/usr/sbin/bgpd
/usr/sbin/isisd
/etc/ramd.conf.new
/etc/ramd.conf.old
/etc/ramd.conf.prev.old
/var/tmp/*/*.pid
/var/tmp/*/*.dump
/var/tmp/*/core
where,
*
can be
ramd
or the routing daemons.