HP-UX Routing Services Administrator's Guide HP-UX 11i v2, HP-UX 11i v3 (B2355-91153, November 2011)

NOTE: The hellointerval value must be the same for all OSPF routers.
• routerdeadinterval specifies the time interval (in seconds) for which the Hello packets
are not received from a router before it is considered down or inactive by its neighbors. This
value must be a multiple of the hellointerval value.
◦ Default: None (you must specify a value)
◦ Range: 0 – 65535
NOTE: The routerdeadinterval value must be the same for all OSPF routers.
You can define a point-to-point interface with or without a nonbroadcast clause. If you
specify the nonbroadcast clause, then you must define the pollinterval statement.
• pollinterval specifies a rate at which hellos are sent when a neighboring router becomes
inactive (a router is considered inactive when hellos have not been received from the router
for the amount of time specified by the routerdeadinterval definition). The value of
pollinterval must be larger than the value of hellointerval. A sample value for an
X.25 network is 2 minutes.
◦ Default: None (you must specify a value)
◦ Range: 0 – 255
If the device at the other end of the point-to-point network is not an OSPF router, you can
prevent sending Hello packets to that OSPF router using the stubhosts statement. stubhosts
specifies the IP address or domain name of the non-OSPF host. The cost of sending a packet
to the host must also be specified (in most cases, the host has only a single connection to the
network, so the cost configured has no effect on routing).
Figure 11 shows an example of a router (A) that is connected to a non-broadcast, point-to-point
network through interface 193.2.1.1.
Figure 11 Point-to-Point Router Interface Example
The following is an example of the interface definition in router A’s /etc/gated.conf file:
interface 193.2.1.1 nonbroadcast cost 5 {
hellointerval 30 ;
routerdeadinterval 30 ;
retransmitinterval 30 ;
pollinterval 30 ;
} ;
If the router A is connected to a multicast, point-to-point network, you must omit the nonbroadcast
clause and the pollinterval statement.
Stub Areas
By default, AS external link advertisements (routes to destinations outside the AS) are propagated
to every router in every area in the AS. You can configure certain OSPF areas as stub areas. AS
external link advertisements are not flooded through stub areas. This reduces the size of the topology
database that must be maintained by internal routers in the stub area and reduces the protocol
traffic through the area. For example, if all the inter-area traffic for an area must go through a
single router, then it is not necessary for all routers in the area to receive inter-area routing
information.
Configuring the OSPF Protocol 35