Installing and Administering Internet Services

Chapter 8 297
Configuring gated
Troubleshooting gated
Once tracing is started to a file, the trace file can be rotated. Receipt of a
SIGUSR1 signal causes gated to stop tracing and closes the trace file.
The trace file can then be moved out of the way. To send a SIGUSR1
signal to gated, issue one of the following commands:
/usr/bin/kill -SIGUSR1 pid
or
/usr/bin/kill -USR1 pid
where pid is gated’s process ID, determined by invoking the command
ps -ef | grep gated.
A subsequent SIGUSR1 signal starts tracing again to the same trace file.
If the trace options are changed before tracing is started up again, the
new options will take effect.
NOTE You cannot use the SIGUSR1 signal if tracing to a file has not previously
been specified when starting gated.
gated Routing Table
Sending gated a SIGINT signal causes gated to write out its
information in /var/tmp/gated_dump. The information includes the
interface configurations, tasks information for each protocol, and the
routing tables.
ripquery
/usr/sbin/ripquery is a support tool that can be used to query gated
for RIP routing information. ripquery sends out two types of
commands: a POLL command or a RIP request command. gated
responds to a POLL command by listing all routes learned from RIP that
are in its routing table. This does not include the interface routes for the
local network or routes from other protocols that are announced via RIP.
When gated receives a RIP request command, it announces routes via
RIP on that interface. This includes routes from other protocols that are
being imported by gated on the node.
You can use ripquery to query other non-gated RIP routers. To do so,
you may need to use the -p option. This option causes ripquery to
initially send POLL commands and then, if there is no response, send RIP
request commands. The default query (POLL commands) sent by
ripquery may not be supported by all RIP routers. Type man 1M
ripquery at the HP-UX prompt for more information.