HP-UX Routing Services Administrator's Guide HP-UX 11i v2, HP-UX 11i v3 (B2355-91153, November 2011)
Troubleshooting gated
This section describes the following techniques for troubleshooting gated and some common
problems encountered with gated operation:
• “Checking for Syntax Errors in the Configuration File” (page 49)
• “Tracing gated Activity” (page 49)
• “Operational User Interface for gated – gdc” (page 50)
• “The gated Routing Table” (page 50)
• “The ripquery Tool” (page 50)
• “The ospf_monitor Tool” (page 50)
• “Common Problems” (page 50)
Checking for Syntax Errors in the Configuration File
After creating or modifying a gated configuration file, you must start gated from the command
line with the -C option. This option parses the the configuration file for syntax errors.
Tracing gated Activity
gated prints information about its activity in the form of tracing output. This information includes
routes that gated reads, adds, and deletes from the kernel routing table, as well as packets sent
and received.
You can specify tracing either with the gated -t command-line option or with the traceoptions
statement in the /etc/gated.conf file. Using any of the following combinations, you can
determine where the tracing output is printed and whether tracing is performed:
• If you specify trace options and a trace file, tracing output is printed to the log file.
• If you specify trace options but do not specify a trace file, tracing output is printed on the
display where gated was started.
• If you specify a trace file but do not specify any trace options, no tracing takes place.
NOTE: In gated 3.5.9, the two statements in the Trace class (tracefile and traceoptions)
are combined into one traceoptions statement. Therefore, the tracefile statement is
eliminated. For details about the new syntax, type man 4 gated.conf at the HP-UX prompt.
After tracing is started to a file, you can rotate the trace file. Receipt of a SIGUSR1 signal stops
gated from 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 the 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 again, the new options are used.
NOTE: You cannot use the SIGUSR1 signal if you did not previously specify tracing to a file
while starting gated.
Troubleshooting gated 49