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

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

131

132

133

134

135

136

137

138

139

140

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

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 speciﬁed, only routes to attached interfaces will be exported. If any policy is speciﬁed,

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 ﬁlters 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

speciﬁed, they are processed from most general (protocol) to most speciﬁc (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 speciﬁed, RIP and interface routes are exported into RIP and HELLO and interface

routes are exported into HELLO. If any policy is speciﬁed, 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 capa-

ble 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 sufﬁcient. 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 ]

[ metric metric ] {

export_list ;

};

It is not possible to create OSPF intra- or inter-area routes by exporting routes from the GateD routing

table into OSPF. It is only possible to export from the GateD routing table into OSPF ASE routes. It is also

not possible to control the propagation of OSPF routes within the OSPF protocol.

There are two types of OSPF ASE routes, type 1 and type 2, see the OSPF protocol conﬁguration for a

detailed explanation of the two types. The default type is speciﬁed by the defaults subclause of the ospf

clause. This may be overridden by a speciﬁcation on the export statement.

HP-UX 11i Version 1: September 2005 − 46 − Hewlett-Packard Company Section 4−−115