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

g
gated.conf(4) gated.conf(4)
configured, at least one must the be backbone. The backbone may only be configured using the
backbone keyword, it may not be specified as area 0. The backbone interface may be a virtual-
link.
authtype 0 | 1 | none | simple
OSPF specifies an authentication scheme per area. Each interface in the area must use this same
authentication scheme although it may use a different authenticationkey. The currently
valid values are none (0) for no authentication, or simple (1) for simple password authentica-
tion.
stub [ cost cost]
A stub area is one in which there are no ASE routes. If a cost is specified, this is used to
inject a default route into the area with the specified cost.
networks
The networks list describes the scope of an area. Intra-area LSAs that fall within the specified
ranges are not advertised into other areas as inter-area routes. Instead, the specified ranges are
advertised as summary network LSAs. If restrict is specified, the summary network LSAs are
not advertised. Intra-area LSAs that do not fall into any range are also advertised as summary
network LSAs. This option is very useful on well designed networks in reducing the amount of
routing information propagated between areas. The entries in this list are either networks, or a
subnetwork/mask pair. See the section on Route Filtering for more detail about specifying
ranges.
stubhosts
This lists specifies directly attached hosts that should be advertised as reachable from this router
and the costs they should be advertised with. Point-to-point interfaces on which it is not desir-
able to run OSPF should be specified here.
It is also useful to assign a additional address to the loopback interface (one not on the 127 net-
work) and advertise it as a stub hosts. If this address is the same one used as the router-id, it
enables routing to OSPF routers by router-id, instead of by interface address. This is more reli-
able than routing to one of the routers interface addresses which may not always be reachable.
interface interface_list [cost cost ]
This form of the interface clause is used to configure a broadcast (which requires IP multicast
support) or a point-to-point interface. See the section on interface list specification for the
description of the interface_list.
Each interface has a cost. The costs of all interfaces a packet must cross to reach a destination
are summed to get the cost to that destination. The default cost is one, but another non-zero
value may be specified.
Interface parameters common to all types of interfaces are:
retransmitinterval time
The number of seconds between link state advertisement retransmissions for adjacen-
cies belonging to this interface.
transitdelay time
The estimated number of seconds required to transmit a link state update over this
interface. Transitdelay takes into account transmission and propagation delays and
must be greater than 0.
priority priority
A number between 0 and 255 specifying the priority for becoming the designated
router on this interface. When two routers attached to a network both attempt to
become designated router, the one with the highest priority wins. A router whose
router priority is set to 0 is ineligible to become designated router.
hellointerval time
The length of time, in seconds, between Hello packets that the router sends on the
interface.
routerdeadinterval time
The number of seconds not hearing Hello packets of a router before the neighbors of
the router will declare it down.
Section 4−−90 Hewlett-Packard Company − 21 − HP-UX 11i Version 1: September 2005