HP Routing Services -UX 11i v2 Common Problems, Problem 1 gated does not act as expected, 104

Configuring gated

Troubleshooting gated

Common Problems

This section discusses the common problems experienced during gated operation.

Problem 1: gated does not act as expected.

First, check the syslogd output for any syntax errors that may have been flagged.

To detect incorrect configuration commands, use gated tracing. Following are two sample configurations, along with the trace files generated by gated. The node used has three interfaces: lan0, lan1, and lan2. In the configuration files, lan0, lan1, and lan3 are specified. In the first configuration shown, the strictintfs option is specified for the interfaces to ensure that gated exits when the error is detected.

Interface Configuration With strictintfs Option Specified The following configuration references a non-existent interface. The options strictintfs line in the interfaces statement ensures that all the configured interfaces exit before gated starts.

traceoptions "tt" general; interfaces {

options strictintfs ;

interface lan0 lan1 lan3 passive ;

} ;

rip yes ;

The following is the tracing output that is produced when gated is started with this configuration:

trace_on: Tracing to "/tt" started

Tracing flags enabled: general

parse: conf.tt:4 Interface not found at ’lan3’

parse_parse: 2 parse errors

Exit gated[15941] version @(#)Revision: 1.0 based on Cornell G ateD R3_5Beta_3

104 Chapter 3