| 26.4. Examples of RIP configuration | ||
|---|---|---|
 | Chapter 26. RIP - Routing Information Protocol |  |
| 26.4. Examples of RIP configuration | ||
|---|---|---|
| | Chapter 26. RIP - Routing Information Protocol | |
This section describes a typical example of RIP application.
The purpose is:
To ensure automatic switch to the backup connection between two remote sites, when primary link is down; in one of the two sites primary and backup connection aren't managed by the same router.
In the chart we find the following elements:
Site 1
Abilis-1P: router that manages the primary connection with Abilis-2;
Abilis-1B: router that manages the backup connection with Abilis-2.
Site 2
Abilis2: remote router connected to Site1 with a primary and a backup link.
In this example isn't required to analyze the kind of connection between the two sites.
In the following sections will be shown how to configure the Abilis of “Site 1”:
Activation of RIP resources.
Configuration of RIP resources.
Configuration of IP and IP Router resources.
Display IP routing tables.
In this example won't be necessary to use the RIP External Routes filter table: it means that the general rule will be “accept”.
Add the RIP resource on both Abilis of “Site1” with the following command; the RIP resource may already exist in the system, but may not yet be active: set it active with the command s act res:rip.
Abilis-1P:
[15:43:30] ABILIS_1P:a res:ripRES:RIP ALREADY EXISTS[16:02:48] ABILIS_1P:s act res:ripCOMMAND EXECUTED
![[Caution]](../images/caution.png) | Caution |
|---|---|
After adding or setting the RIP active, you must restart the Abilis to make the resource running (use the command warm start to reboot the Abilis). |
[11:01:39] ABILIS_CPX:s p rip act:yesCOMMAND EXECUTED [11:01:39] ABILIS_CPX:d p ripRES:Rip - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------- ------------------------------------------------------------------------ Run DESCR:Routing_Information_Protocol LOG:NO ACT:YES locport:520 fifo:15 max-routes:500 SH:PR AUT:NO PWD: UT:30 LT:180 GT:120 ASBR:YES - ASBR section --------------------------------------------------------- LOCAL:YES STATIC:YES OSPF:NO LOCAL-METRIC:* STATIC-METRIC:* OSPF-METRIC:* DEF-METRIC:1
Abilis-1B:
Repeat the same procedure for Abilis-1B.
Abilis-1P:
Abilis-1P is the Abilis that manage the primary link to Abilis2, so its metric default value must be the lowest one: it will be left to default value 1. So, on this Abilis is enough to enable the resource.
Abilis-1B:
Abilis-1B is the Abilis that manage the backup link to Abilis-2, so its metric default value must be higher the Abilis-1P one: it will be set to the value 3.
[11:01:39] ABILIS_CPX:s p rip def-metric:3COMMAND EXECUTED [11:01:39] ABILIS_CPX:d p ripRES:Rip - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------- ------------------------------------------------------------------------ Run DESCR:Routing_Information_Protocol LOG:NO ACT:YES locport:520 fifo:15 max-routes:500 SH:PR AUT:NO PWD: UT:30 LT:180 GT:120 ASBR:YES - ASBR section --------------------------------------------------------- LOCAL:YES STATIC:YES OSPF:NO LOCAL-METRIC:* STATIC-METRIC:* OSPF-METRIC:* DEF-METRIC:3
With this command we have assigned to all the IP routings of Abilis-1B the metric value 3, so they will be exported with this cost.
Now indicating on which IP resources the RIP protocol is to be active is needed.
The Abilis-1P and Abilis-1B are connected on the same Ethernet
LAN, so we have to active RIP on the corresponding IP resources
(res:ip-1).
The parameters which must be set are:
RPIt's used to activate/deactivate routing protocols on this
interface; when RIP protocol is selected, the
specific parameter section will be activated.
RIPSENDIt sets the protocol used for sending RIP updates
[RIP1, RIP2B,
NO];
RIPRECVIt sets the protocol accepted for receiving RIP updates
[RIP1, RIP2,
BOTH, NO];
RIPNU (normal update)It sets whether RIP updates have to be sent regularly or
only in case of variations;[NO: updates are
sent only if the routing table is changed,YES:
updates are sent regularly according to the RIP resource];
RIPMETRICIt sets the metric associated to IP port according to meant and the rules prescribed by the routing algorithm RIP.
Abilis-1P:
[09:37:33] ABILIS_1P:s p ip-1 rp:ripCOMMAND EXECUTED[09:37:45] ABILIS_1P:d p ip-1RES:Ip-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------ Run DESCR: OPSTATE:UP LOG:NO STATE-DETECT:NORMAL LANRES:Eth-1 IPADD:192.168.001.254 MASK:255.255.255.000 REDIS:YES HIDE:NO RP:RIP IPSEC:NO VRRP:NO NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO OUTBUF:100 OUTQUEUE:FAIR MTU:1500 OUTSPL:NO INBUF:0 mru:1500 SRCV:NO - RIP section ---------------------------------------------------------- RIPSEND:RIP2B RIPRECV:BOTH RIPNU:YES RIPMETRIC:1 - TRFA section --------------------------------------------------------- TRFA:NO - Lan ------------------------------------------------------------------ LLOG:NO arpcache:200 CACHETIMER:120 rxbuf:4 txbuf:14 VLAN-ID:UNTAG RES:Eth-1 --------------------------------------------------------------------- Run DESCR: LOG:DS MODE:AUTO DUPLEX:HALF MAC-ADDR:FACTORY (00-E0-C5-54-A2-78) dma-rxbuf:250 dma-txbuf:25 max-vlans:0 ip-rxbuf:25 arp-rxbuf:5 pppoed-rxbuf:5 pppoes-rxbuf:25
Abilis-1B:
[09:37:33] ABILIS_1B:s p ip-1 rp:ripCOMMAND EXECUTED[09:37:45] ABILIS_1B:d p ip-1Run DESCR: OPSTATE:UP LOG:NO STATE-DETECT:NORMAL LANRES:Eth-1 IPADD:192.168.001.253 MASK:255.255.255.000 REDIS:YES HIDE:NO RP:RIP IPSEC:NO VRRP:NO NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO OUTBUF:100 OUTQUEUE:FAIR MTU:1500 OUTSPL:NO INBUF:0 mru:1500 SRCV:NO - RIP section ---------------------------------------------------------- RIPSEND:RIP2B RIPRECV:BOTH RIPNU:YES RIPMETRIC:1 - TRFA section --------------------------------------------------------- TRFA:NO - Lan ------------------------------------------------------------------ LLOG:NO arpcache:200 CACHETIMER:120 rxbuf:4 txbuf:14 VLAN-ID:UNTAG RES:Eth-1 --------------------------------------------------------------------- Run DESCR: LOG:DS MODE:AUTO DUPLEX:HALF MAC-ADDR:FACTORY (00-E0-C5-54-A2-78) dma-rxbuf:250 dma-txbuf:25 max-vlans:0 ip-rxbuf:25 arp-rxbuf:5 pppoed-rxbuf:5 pppoes-rxbuf:25
| Caution |
|---|---|
To initialize the resources, use the init res:ip-1 command (to set act the changes made on uppercase parameters) and remember to save the configuration to preserve the modifications (save conf). |
It's important take a look also to the IP router configuration:
[10:44:33] ABILIS_1P:d p iprtrRES:Iprtr --------------------------------------------------------------------- Run DESCR:IP_Router_general_properties - General -------------------------------------------------------------- R-ID:AUTO (192.168.029.254) maxroute:500 DFTTTL:255 ps:2048 DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120 pvc:0 bsvc:0 LINKS:6 virtual:0 - IP Access List ------------------------------------------------------- ACL:YES ACLBYPASS:# COS:ENABLED COSDFT:NORMAL COSBALANCE:NO NORMRATE:50 LOWRATE:50 - IPCOS to 802.1q (VLAN) priority -------------------------------------- LOW:1 NORMAL:0 HIGH:5 - Ppp-Dns -------------------------------------------------------------- PPP-DNS-PRI:000.000.000.000 PPP-DNS-SEC:000.000.000.000
The parameter DEF-RIP-AD sets the default value
of the Administrative Distance for
the routes received from RIP.
The parameter DEF-LOCAL-AD sets the default
value of the Administrative Distance
for local-connected routes.
When IPRTR gets routing from different routing protocols, must give them a specific priority. This parameter can be overridden in case of current routing is present in the administrative distance table.
By joining these two parameters, it's possible to complete
configurations: the DEF-LOCAL-AD parameter on
Abilis-1B will have a higher value than the Abilis-1P's one, so that the
local-connected routes of Abilis-1B will have the lowest
priority.
Remember that the aim is to ensure automatic switch to the backup connection between two remote sites. When primary link is down, the Abilis-1B must inform Abilis-1P that the better way to reach the “Site2” is through it, but during the normal working Abilis-1B must know that the way to reach the “Site2” is through Abilis-1P.
On Abilis-1B:
[11:15:43] ABILIS_1B:s p iprtr DEF-LOCAL-AD:180COMMAND EXECUTED[11:50:30] ABILIS_1B:d p iprtrRES:Iprtr --------------------------------------------------------------------- Run DESCR:IP_Router_general_properties - General -------------------------------------------------------------- R-ID:AUTO (192.168.029.254) maxroute:500 DFTTTL:255 ps:2048 DEF-LOCAL-AD:180 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120 pvc:0 bsvc:0 LINKS:6 virtual:0 - IP Access List ------------------------------------------------------- ACL:YES ACLBYPASS:# COS:ENABLED COSDFT:NORMAL COSBALANCE:NO NORMRATE:50 LOWRATE:50 - IPCOS to 802.1q (VLAN) priority -------------------------------------- LOW:1 NORMAL:0 HIGH:5 - Ppp-Dns -------------------------------------------------------------- PPP-DNS-PRI:000.000.000.000 PPP-DNS-SEC:000.000.000.000
| Caution |
|---|---|
To initialize the resources, use the init res:iprtr command (to set act the changes made on uppercase parameters) and remember to save the configuration to preserve the modifications (save conf). |
Now let see what happens in the routing tables of the two Abilis when functioning on primary link and the backup link.
This will be the routings table when primary link is active.
[12:46:18] ABILIS_1P:d iprDestination routes and conditional source routes: +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |B|P|S|H| NET:/MASK: | MASK: or | GW: or IPLB: |IP: |AD:| | | | | | | SRNET:/SRMASK: | | | | +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |*|R| | | 192.168.001.253/32 | 255.255.255.255 | 192.168.001.253 | 1|120| |*|C| | | 192.168.001.254/32 | 255.255.255.255 | |R-ID| 0| |*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0| |*|C| | | 192.168.002.000/24 | 255.255.255.000 | | 5| 0| |*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 3| 1| +-+-+-+-+--------------------+--------------------+-----------------+----+---+
[14:26:47] ABILIS_1B:d iprDestination routes and conditional source routes: +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |B|P|S|H| NET:/MASK: | MASK: or | GW: or IPLB: |IP: |AD:| | | | | | | SRNET:/SRMASK: | | | | +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |*|C| | | 192.168.001.253/32 | 255.255.255.255 | |R-ID|180| |*|R| | | 192.168.001.254/32 | 255.255.255.255 | 192.168.001.254 | 1|120| |*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0| |*|R| | | 192.168.002.000/24 | 255.255.255.000 | 192.168.001.254 | 1|120| | |C| | | 192.168.002.000/24 | 255.255.255.000 | | 5|180| |*|R| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1| +-+-+-+-+--------------------+--------------------+-----------------+----+---+
In this situation Abilis-1B receives from Abilis-1P the route for the Site2's network (192.168.2.0/24): the priority of this route is higher than the route local-connected, so the RIP route will be considered the best.
Otherwise, this will be the routing table when the backup link is operating.
[12:46:18] ABILIS_1P:d iprDestination routes and conditional source routes: +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |B|P|S|H| NET:/MASK: | MASK: or | GW: or IPLB: |IP: |AD:| | | | | | | SRNET:/SRMASK: | | | | +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |*|R| | | 192.168.001.253/32 | 255.255.255.255 | 192.168.001.253 | 1|120| |*|C| | | 192.168.001.254/32 | 255.255.255.255 | |R-ID| 0| |*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0| |*|R| | | 192.168.002.000/24 | 255.255.255.000 | 192.168.001.253 | 1|120| | |C| | | 192.168.002.000/24 | 255.255.255.000 | |D 5| 0| |*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 3| 1| +-+-+-+-+--------------------+--------------------+-----------------+----+---+
[14:26:47] ABILIS_1B:d iprDestination routes and conditional source routes: +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |B|P|S|H| NET:/MASK: | MASK: or | GW: or IPLB: |IP: |AD:| | | | | | | SRNET:/SRMASK: | | | | +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |*|C| | | 192.168.001.253/32 | 255.255.255.255 | |R-ID|180| |*|R| | | 192.168.001.254/32 | 255.255.255.255 | 192.168.001.254 | 1|120| |*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0| |*|C| | | 192.168.002.000/24 | 255.255.255.000 | | 5|180| |*|R| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1| +-+-+-+-+--------------------+--------------------+-----------------+----+---+
In this situation Abilis-1P receives from Abilis-1B the route for
the Site2's network (192.168.2.0/24): the IP resource 5 on Abilis-1P is
declared down (D 5), so the correspondent route won't be
sent by RIP; the RIP route will be considered the best, so the packets
for the remote network will be sent through Abilis-1B.
In this way (supposing that Abilis-1P is the default gateway for the network 192.168.1.0/24), the users in Site1 could reach the Site2's network through the backup link, without change anything on their terminals!
| |  | |
| 26.3. RIP diagnostics and statistics |  | Chapter 27. VRRP - Virtual Router Redundancy Protocol |