HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
g
gated.conf(4) gated.conf(4)
aggregate/generate routes aggregate/generate 130
OSPF AS external routes ospf 150
BGP routes bgp 170
EGP egp 200
Sample Preference Specifications
interfaces {
interface 138.66.12.2 preference 10 ;
};
rip yes {
preference 90 ;
};
import proto rip gateway 138.66.12.1 preference 75 ;
In these statements the preference applicable to routes learned via RIP from gateway 138.66.12.1 is 75.
The last preference applicable to routes learned via RIP from gateway 128.66.12.1 is defined in the accept
statement. The preference applicable to other RIP routes is found in the rip statement. The preference set
on the interface statement applies only to the route to that interface.
Trace Statements
Trace statements control tracing options. The GateD tracing options may be configured at many levels.
Tracing options include the file specifications, control options, and global and protocol specific tracing
options. Unless overridden, tracing options from the next higher level are inherited by lower levels. For
example, BGP peer tracing options are inherited from BGP group tracing options, which are inherited from
global BGP tracing options, which are inherited from global GateD tracing options. At each level tracing
specifications override the inherited options.
Global tracing options
There are two types of global options, those which only affect global operations and those which have poten-
tial significance to protocols.
Global significance only
The trace flags that only have global significance are:
parse Trace the lexical analyzer and parser. Mostly used by GateD developers for debugging.
adv Trace the allocation of and freeing of policy blocks. Mostly used by the GateD developers for
debugging.
symbols Used to trace symbols read from the kernel at startup. The only useful way to specify this
level of tracing is via the -t option on the command line since the symbols are read from
the kernel before parsing the configuration file.
iflist Used to trace the reading of the kernel interface list. It is useful to specify this with the -t
option on the command line since the first interface scan is done before reading the
configuration file.
Protocol significance
The options flags that have potential significance to protocols are:
all Turn on all of the following.
general A shorthand notation for specifying both normal and route.
state Trace state machine transitions in the protocols.
normal Trace normal protocols occurrences. Abnormal protocol occurrences are always traced.
policy Trace application of protocol and user-specified policy to routes being imported and
exported.
task Trace system interface and processing associated with this protocol or peer.
timer Trace timer usage by this protocol or peer.
route Trace routing table changes for routes installed by this protocol or peer.
Not all of the above options apply to all of the protocols. In some cases their use does not make sense (for
instance, RIP does not have a state machine) and in some instances the requested tracing has not been
HP-UX Release 11i: December 2000 − 4 − Section 4−−75
___
___