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)
The Export Statement
The import statement controls which routes received from other systems are used by GateD, and the
export statement controls which routes are advertised by GateD to other systems. Like the import state-
ment, the syntax of the export statement varies slightly per protocol. The syntax of the export state-
ment is similar to the syntax of the import statement, and the meanings of many of the parameters are
identical. The main difference between the two is that while route importation is just controlled by source
information, route exportation is controlled by both destination and source.
The outer portion of a given export statement specifies the destination of the routing information you are
controlling. The middle portion restricts the sources of importation that you wish to consider. And the
innermost portion is a route filter used to select individual routes.
Specifying metrics
The most specific specification of a metric is the one applied to the route being exported. The values that
may be specified for a metric depend on the destination protocol that is referenced by this export state-
ment.
restrict
metric metric
restrict
Specifies that nothing should be exported. If specified on the destination portion of the export
statement, it specifies that nothing at all should be exported to this destination. If specified on
the source portion, it specifies that nothing from this source should be exported to this destina-
tion. If specified as part of a route filter, it specifies that the routes matching that filter should
not be exported.
metric metric
Specifies the metric to be used when exporting to the specified destination.
Route Filters
All the formats allow route filters as shown below. See the section on route filters for a detailed explanation
of how they work. When no route filtering is specified (when restrict is specified on the first line of a
statement), all routes from the specified source will match that statement. If any filters are specified, only
routes that match the specified filters will be exported. Put differently, if any filters are specified, an all
restrict ; is assumed at the end of the list.
network [ exact | refines ]
network mask mask [exact | refines ]
network masklen number [ exact | refines ]
default
host host
Specifying the destination
As mentioned above, the syntax of the export statement varies depending on the protocol it is being
applied to. One thing that applies in all cases is the specification of a metric. All protocols define a default
metric to be used for routes being exported, in most cases this can be overridden at several levels of the
export statement.
The specification of the source of the routing information being exported (the export_list) is described
below.
Exporting to EGP and BGP
export proto bgp | egp as autonomous system
restrict ;
export proto bgp | egp as autonomous system
[ metric metric ] {
export_list ;
};
Exportation to EGP and BGP is controlled by autonomous system, the same policy is applied to all routers
in the AS. EGP metrics range from 0 to 255 inclusive with 0 being the most attractive.
BGP metrics are 16 bit unsigned quantities. They range from 0 to 65535 inclusive with 0 being the most
attractive. While BGP version 4 actually supports 32 bit unsigned quantities, GateD does not yet support
this.
Section 4−−116 − 45 − HP-UX Release 11i: December 2000
___
___