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

input_config_file_name is the name of the gated 3.0 file you want to convert. You
must specify this name, because the tool does not assume that you are converting the default
file, /etc/gated.conf.
output_config_file is the name of the new configuration file for gated 3.5.9. You must
specify this name, because the tool does not assume that you are coverting the default file,
/etc/gated.conf.
For example, to convert the gated 3.0 configuration file to gated 3.5.9, issue the following
command:
conv_config < /etc/gated.conf.30 > /etc/gated.conf
After running the conversion tool, you can check the new configuration file for compatibility using
the gated -c command. See the Note in the section “Configuration Overview” (page 19) for
more information.
Configuring the RIP Protocol
RIP uses hopcount to determine the shortest path to a destination. Hopcount is the number of routers
a packet must pass through to reach its destination. If a path is directly connected, it has the lowest
hopcount of 1. If the path passes through a single router, the hopcount increases to 2. Hopcount
can increase to a maximum value of 16, which is RIP’s infinity metric, an indication that a network
or node cannot be reached.
If gated encounters an unreachable node, it goes into Holddown Mode. Holddown Mode stops
a node from propagating routing information until the other nodes that it is communicating with
stabilize their routing information.
Hosts with only one LAN interface may use the RIP protocol with gated to passively listen to routing
information when multiple routers on the LAN exist. If only one router on the LAN exists (leaving
only one path off the local LAN), you can configure a static route to that router in the
/etc/rc.config.d/net file, or issue the route command manually, instead of running gated.
In certain cases, you may not want the traffic to follow a certain path, because it incurs an
unacceptable cost or security risk. In these cases, gated allows you to assign a metric to each
interface. This allows you to select or bypass a path, irrespective of its length or speed.
RIP Protocol Statement
The syntax of the RIP protocol statement is as follows:
rip yes|no | on|off [ {
broadcast|nobroadcast ;
nocheckzero ;
preference preference ;
defaultmetric metric ;
query authentication [none|[[simple|md5] password]] ;
interface interface_list
[noripin]|[ripin] [noripout]|[ripout]
[metricin metric] [metricout metric]
[version 1]|[version 2 [multicast|broadcast]]
[[secondary] authentication [none [simple|md5] password]] ;
[interface ...]
trustedgateways router_list ;
sourcegateways router_list ;
traceoptions traceoptions ;
} ] ;
Curly braces ({}) are part of the syntax for the RIP protocol statement. Square brackets ([]) are not
part of the syntax; they are used here to indicate optional parameters.
yes (or on) informs gated to enable the RIP protocol at this node and to process RIP packets
coming in from other nodes. no (or off) informs gated to disable the RIP protocol at this node.
If gated finds fewer than two network interfaces, the node listens to RIP information. If gated
22 Configuring gated