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

lan2 Index 3 Address 802.2 8:0:9:3d:2c:b1 Change: <> State: <>
Refcount: 2 Up-down transitions: 0
198.1.1.17
Metric: 0 MTU: 1436
Refcount: 4 Preference: 0 Down: 120
Change: <> State: <Up Broadcast Multicast>
Broadcast Address: 198.1.1.255
Subnet Number: 198.1.1 Subnet Mask: 255.255.255
lan1 Index 4 Address 802.2 8:0:9:3d:3c:69 Change: <> State: <>
Refcount: 2 Up-down transitions: 0
198.2.1.40
Metric: 0 MTU: 1436
Refcount: 4 Preference: 0 Down: 120
Change: <> State: <Up Broadcast Multicast NoAge>
Broadcast Address: 198.2.1.255
Subnet Number: 198.2.1 Subnet Mask: 255.255.255
Interface policy:
Interface lan0 lan1 lan3 passive
The state recorded in lan2 does not contain the NoAge flag, because the interface was not set to
passive in the interface policy statement.
A common mistake is to expect gated to always send out RIP packets when you specify rip yes
in a configuration file. gated will be an active RIP participant only if the host is a router (that is,
when the host has more than one network interface).
Problem 2: gated deletes routes from the routing table.
gated maintains a complete routing table in user space, and synchronizes this table with the
kernel routing table. When gated starts, it reads the entries in the kernel routing table. However,
if gated does not get confirmation from its routing protocols (RIP, OSPF, and so on) about a route,
it deletes the route from its tables and from the kernel routing table.
Normally, gated deletes the route configured in the /etc/rc.config.d/netconf file. To solve
this problem, configure a static default route as described in the section “Installing Static Routes”
(page 45).
Another common scenario occurs in networks where all the gateways do not implement the gated
routing protocols. In this situation, routes that do not use gated gateways are not confirmed by
gated, and gated deletes them unless a static statement is included in /etc/gated.conf:
static {
13.0.0.0 mask 0xff000000 gateway 15.14.14.14 ;
};
The static entry in this example ensures that the local system includes a route to network 13.0.0.0
even though the gateway to that network (15.14.14.14) is not running any of the gated protocols.
You can include the restrict clauses in the export statements to restrict these extra routes from
being advertised.
Problem 3: gated adds routes that appear to be incorrect.
If gated adds routes that appear to be incorrect, track the original source of the route by completing
the following steps:
1. Start by looking at the routing table maintained by gated.
2. Send gated a SIGINT signal, and look at the information output in the
/var/tmp/gated_dump file.
3. Look for the entry of the route in question. The entry identifies the protocol over which this
route was heard and the first-hop router. The first-hop router is likely to be the immediate source
of the information.
52 Configuring gated