HP-UX Reference (11i v1 05/09) - 4 File Formats (vol 8)

g
gated.conf(4) gated.conf(4)
options option_list
Configure kernel options. The valid options are:
nochange
On systems supporting the routing socket this insures that changes operations will
not be performed, only deletes and adds. This is useful on early versions of the routing
socket code where the change operation was broken.
noflushatexit
During normal shutdown processing GateD deletes all routes from the kernel forward-
ing table that do not have a retain indication. The noflushatexit option prevents
route deletions at shutdown. Instead, routes are changed and added to make sure that
all the routes marked with retain get installed.
This is handy on systems with thousands of routes. Upon startup GateD will notice
which routes are in the kernel forwarding table and not have add them back.
remnantholdtime time
Normally remnant routes read from the kernel forwarding table at startup are timed
out in three minutes or as soon as they are overridden. This option allows the interval
to be configured to a value between zero and 15 minutes. Setting it to zero causes
these routes to be deleted immediately.
routes number
On some systems kernel memory is at a premium. With this parameter a limit can be placed on
the maximum number of routes GateD will install in the kernel. Normally gated
adds/changes/deletes routes in interface/internal/external order. It queues interface routes first,
followed by internal routes, followed by external routes, and processes the queue from the begin-
ning. If a this parameter is specified and the limit is hit, GateD does two scans of the list instead.
On the first scan it does deletes, and also deletes all changed routes, turning the queued changes
into adds. It then rescans the list doing adds in interface/internal/external order until it hits the
limit again. This will tend to favor internal routes over external routes. The default is not to
limit the number of routes in the kernel forwarding table.
flash
When routes change, the process of notifying the protocols is called a flash update. The kernel
forwarding table interface is the first to be notified. Normally a maximum of 20 interface routes
may be processed during one flash update. The flash command allows tuning of these parame-
ters.
limit number
Specifies the maximum number of routes which may be processed during one flash
update. The default is 20. A value of -1 will cause all pending route changes of the
specified type to be processed during the flash update.
type interface | interior | all
Specifies the type of routes that will be processed during a flash update. Interior
specifies that interior routes (See the definition of interior gateway protocols) will also
be installed. All specifies the inclusion of exterior routes (See the definition of exte-
rior gateway protocols) as well. The default is interface which specifies that only
interface routes will be installed during a flash update.
Specifying flash limit -1 all causes all routes to be installed during the flash update; this
mimics the behavior of previous versions of GateD.
background
Since only interface routes are normally installed during a flash update, the remaining routes
are processed in batches in the background, that is, when no routing protocol traffic is being
received. Normally, 120 routes are installed at a time to allow other tasks to be performed and
this background processing is done at lower priority than flash updates the following parameters
allow tuning of these parameters:
limit number
Specifies the number of route which may be processed at during one batch. The
default is 120.
priority flash | higher | lower
Specifies the priority of the processing of batches of kernel updates in relationship to
Section 4−−108 Hewlett-Packard Company − 39 − HP-UX 11i Version 1: September 2005