Configuring the gated daemon
When configuring the gated daemon, you must decide which gateway protocols are most appropriate for your system.
To configure the gated daemon:
- Decide which gateway protocols are most appropriate for
your system. The choices for routing protocols are EGP, BGP, RIP, RIPng, HELLO, OSPF, ICMP/Router Discovery, and IS-IS. You can also use SNMP, a protocol allowing you to change or show management information for a network element from a remote host.Note: Use EGP, BGP, or BGP4+ to advertise addresses of networks in an autonomous system to gateways in other autonomous systems. If you are on the Internet, EGP, BGP, or BGP4+ must be used to advertise network reachability to the core gateway system. Use the interior routing protocols to advertise reachability information within an autonomous system.
- Identify any known networks by listing them in the /etc/networks file.
See Networks File Format for TCP/IP in Files Reference for more information. A sample networks file is located in the /usr/samples/tcpip directory.
- Edit the /etc/gated.conf file to reflect
the desired gated daemon configuration. Note: The gated Daemon version on AIX® 4.3.2 and higher is 3.5.9. The syntax of the /etc/gated.conf file has changed. The examples given below are for the 3.5.9 version of gated. To configure the /etc/gated.conf file for versions prior to AIX 4.3.2, use the syntax provided in the /etc/gated.conf file itself.
- Specify the level of trace output you want. If tracing is needed before the gated.conf file is parsed, use the -t flag to turn tracing on when the daemon starts.
- Specify the routing protocols you want to use.
Each protocol has its own protocol statement. Remove the comment symbols (
#
) and modify the statements corresponding to the protocols you want to use.- If using EGP:
- Set up the EGP
autonomoussystem
clause. Obtain an autonomous system number from the Internet authority if you are on the Internet, or if not, assign an autonomous system number considering the autonomous system numbers of other systems on your network. - Set the EGP statement to
yes
. - Set up a
group
clause for each autonomous system. - Set up a
neighbor
clause for each neighbor in that autonomous system. For example:autonomoussystem 283 ; egp yes { group maxup 1 { neighbor nogendefault 192.9.201.1 ; neighbor nogendefault 192.9.201.2 ; } ; group { neighbor 192.10.201.1 ; neighbor 192.10.201.2 ; } ; } ;
- Set up the EGP
- If using RIP or HELLO:
- Set the RIP or HELLO statement to
yes
. - Specify
nobroadcast
in the RIP or HELLO statement if you want the gateway only to accept routing information, not broadcast information. Or specifybroadcast
in the RIP or HELLO statement if you want the gateway to broadcast routing information as well as accept routing information. - If you want the gateway to send directly to source gateways, use
the
sourcegateways
statement. Specify a gateway name or Internet address in dotted decimal in thesourcegateways
clause. For example:# Send directly to specific gateways rip/hello yes { sourcegateways 101.25.32.1 101.25.32.2 ; } ;
The following example shows the RIP/HELLO stanza in the gated.conf file of a machine that does not send RIP packets, and does not receive RIP packets on its tr0 interface.
rip/hello nobroadcast { interface tr0 noripin ; } ;
- Set the RIP or HELLO statement to
- If using BGP:
- Set up the BGP
autonomoussystem
clause. Obtain an autonomous system number from the Internet authority if you are on the Internet, or if not, assign an autonomous system number considering the autonomous system numbers of other systems on your network. - Set the BGP statement to
yes
. - Set up a
peer
clause for each neighbor in that autonomous system. For example:# Perform all BGP operations bgp yes { peer 192.9.201.1 ; } ;
- Set up the BGP
- If using SNMP:
- Set the SNMP statement to
yes
.snmp yes ;
- Set the SNMP statement to
- If using EGP: