HP-UX Reference (11i v2 03/08) - 4 File Formats (vol 8)

g
gated.conf(4) gated.conf(4)
The importation of RIP, HELLO and Redirect routes may be controlled by any of protocol, source inter-
face and source gateway. If more than one is specified, they are processed from most general (protocol) to
most specific (gateway).
RIP and HELLO do not support the use of preference to choose between routes of the same protocol. That
is left to the protocol metrics. These protocols do not save routes that were rejected since they have short
update intervals.
Importing routes from OSPF
import proto ospfase [ tag ospf_tag ] restrict ;
import proto ospfase [ tag ospf_tag ]
[ preference preference ] {
route_filter [ restrict |(preference preference )];
};
Due to the nature of OSPF, only the importation of ASE routes may be controlled. OSPF intra- and inter-
area routes are always imported into the gated routing table with a preference of 10. If a tag is specified,
the import clause will only apply to routes with the specified tag.
It is only possible to restrict the importation of OSPF ASE routes when functioning as an AS border
router. This is accomplished by specifying an export ospfase clause. Specification of an empty export
clause may be used to restrict importation of ASEs when no ASEs are being exported.
Like the other interior protocols, preference can not be used to choose between OSPF ASE routes, that is
done by the OSPF costs. Routes that are rejected by policy are stored in the table with a negative prefer-
ence.
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
statement, the syntax of the export statement varies slightly per protocol. The syntax of the export
statement 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 destination. 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 explana-
tion 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 ]
HP-UX 11i Version 2: August 2003 − 45 − Hewlett-Packard Company Section 4−−121