HP-UX Reference (11i v2 03/08) - 4 File Formats (vol 8)
g
gated.conf(4) gated.conf(4)
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.
If no export policy is specified, only routes to attached interfaces will be exported. If any policy is
specified, the defaults are overridden; it is necessary to explicitly specify everything that should be
exported.
Note that EGP and BGP versions 2 and 3 only support the propagation of natural networks, so the host
and default route filters are meaningless. BGP version 4 supports the propagation of any destination
along with a contiguous network mask.
Exporting to RIP and HELLO
export proto rip | hello
[(interface interface_list )|(gateway gateway_list )]
restrict ;
export proto rip | hello
[(interface interface_list )|(gateway gateway_list )]
[ metric metric ] {
export_list ;
};
Exportation to RIP and HELLO is controlled by any of protocol, interface or gateway. If more than one is
specified, they are processed from most general (protocol) to most specific (gateway).
It is not possible to set metrics for exporting RIP routes into RIP, or exporting HELLO routes into
HELLO. Attempts to do this are silently ignored.
If no export policy is specified, RIP and interface routes are exported into RIP and HELLO and interface
routes are exported into HELLO. If any policy is specified, the defaults are overridden. It is necessary to
explicitly specify everything that should be exports.
RIP version 1 and HELLO assume that all subnets of the shared network have the same subnet mask so
they are only able to propagate subnets of that network. RIP version 2 removes that restriction and is
capable of propagating all routes when not sending version 1 compatible updates.
To announce routes which specify a next hop of the loopback interface (static and internally generated
default routes) via RIP or HELLO, it is necessary to specify the metric at some level in the export
clause. Just setting a default metric for RIP or HELLO is not sufficient. This is a safeguard to verify that
the announcement is intended.
Exporting to OSPF
export proto ospfase [ type 1 | 2 ][tag ospf_tag ]
restrict ;
export proto osfpase [ type 1 | 2 ][tag ospf_tag ]
Section 4−−122 Hewlett-Packard Company − 46 − HP-UX 11i Version 2: August 2003