HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

121

122

123

124

125

126

127

128

129

130

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man4/!!!intro.4

________________________________________________________________

___ ___

gated.conf(4) gated.conf(4)

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 conﬁgured 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 ﬁrst,

followed by internal routes, followed by external routes, and processes the queue from the begin-

ning. If a this parameter is speciﬁed and the limit is hit, GateD does two scans of the list instead.

On the ﬁrst 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 ﬂash update. The kernel

forwarding table interface is the ﬁrst to be notiﬁed. Normally a maximum of 20 interface routes

may be processed during one ﬂash update. The flash command allows tuning of these parame-

ters.

limit number

Speciﬁes the maximum number of routes which may be processed during one ﬂash

update. The default is 20. A value of -1 will cause all pending route changes of the

speciﬁed type to be processed during the ﬂash update.

type interface | interior | all

Speciﬁes the type of routes that will be processed during a ﬂash update. Interior

speciﬁes that interior routes (See the deﬁnition of interior gateway protocols) will also

be installed. All speciﬁes the inclusion of exterior routes (See the deﬁnition of exte-

rior gateway protocols) as well. The default is interface which speciﬁes that only

interface routes will be installed during a ﬂash update.

Specifying flash limit -1 all causes all routes to be installed during the ﬂash update; this

mimics the behavior of previous versions of GateD.

background

Since only interface routes are normally installed during a ﬂash update, the remaining routes

are processed in batches in the background, that is, when no routing protocol trafﬁc 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 ﬂash updates the following parameters

allow tuning of these parameters:

limit number

Speciﬁes the number of route which may be processed at during one batch. The

default is 120.

priority flash | higher | lower

Speciﬁes the priority of the processing of batches of kernel updates in relationship to

the ﬂash update processing. The default is lower which means that ﬂash updates are

processed ﬁrst. To process kernel updates at the same priority as ﬂash updates,

specify flash; to process them at a lower priority, use lower.

Tracing options

While the kernel interface is not technically a routing protocol, in many cases it is handled as one. The fol-

lowing two symbols make sense when entered from the command line since the code that uses them is exe-

cuted before the trace ﬁle is parsed.

symbols

Symbols read from the kernel, by nlist() or similar interface.

Section 4−−110 − 39 − HP-UX Release 11i: December 2000

___