RIP configuration examples

 

·     Introduction

·     Prerequisites

·     Example: Configuring RIP

 

The following information provides RIP configuration examples.

 

This document is not restricted to specific software or hardware versions. Procedures and information in the examples might be slightly different depending on the software or hardware version of the device.

The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

The following information is provided based on the assumption that you have basic knowledge of the RIP feature.

Network configuration

As shown in Figure 1, an enterprise deploys Device A and Device B for the R&D and financial departments, respectively. Device A also acts as the gateway to the Internet.

Configure RIP for the departments to learn routes from each other. Configure a default route on Device A, with the next hop pointing to the gateway address 200.2.2.254, and redistribute the default route to RIP.

Figure 1 Network diagram

 

Software versions used

This configuration example was created and verified on R8860 of the F1000-AI-55 device.

Restrictions and guidelines

RIP updates routing table information through multicast. You must configure a security policy to permit the traffic between the local security zone and the security zone that contains the RIP interface. For more information, see the configuration procedure.

Procedure

Configuring Device A

1.     Assign IP addresses to interfaces and add the interfaces to security zones.

# On the top navigation bar, click Network.

# From the navigation pane, select Interface Configuration > Interfaces.

# Click the Edit icon for GE 1/0/1.

# In the dialog box that opens, configure the interface:

a.     On the Basic Configuration tab, select the Untrust security zone.

b.     On the IPv4 Address tab, enter the IP address and mask of the interface. In this example, enter 10.0.0.1/24.

c.     Click OK.

# Add GE 1/0/2 to the Trust security zone and set its IP address to 10.1.1.1/24 in the same way you configure GE 1/0/1.

# Add GE 1/0/3 to the Untrust security zone and set its IP address to 200.2.2.1/24 in the same way you configure GE 1/0/1.

2.     Create security policies.

# On the top navigation bar, click Policies.

# From the navigation pane, select Security Policies > Security Policies.

# Select Create > Create a policy.

# In the dialog box that opens, configure security policy rip-a:

a.     Enter policy name rip-a.

b.     Select source zone Trust.

c.     Select destination zone Untrust.

d.     Select type IPv4.

e.     Select action Permit.

f.     Enter source IPv4 address 10.1.1.0/24.

g.     Click OK.

# Configure security policy rip-b:

a.     Enter policy name rip-b.

b.     Select source zone Local.

c.     Select destination zone Untrust.

d.     Select type IPv4.

e.     Select action Permit.

f.     Click OK.

# Configure security policy rip-c:

a.     Enter policy name rip-c.

b.     Select source zone Untrust.

c.     Select destination zone Local.

d.     Select type IPv4.

e.     Select service object group rip.

f.     Select action Permit.

g.     Click OK.

# Configure security policy rip-d:

a.     Enter policy name rip-d.

b.     Select source zone Untrust.

c.     Select destination zone Untrust.

d.     Select type IPv4.

e.     Enter source IPv4 address 10.2.2.0/24.

f.     Select action Permit.

g.     Click OK.

3.     Configure a default route to the ISP.

# On the top navigation bar, click Network.

# From the navigation pane, select Routing > Static Routing.

# Click Create.

# In the dialog box that opens, configure a static route as shown in Figure 3.

Figure 2 Creating a static route

 

# Click OK.

4.     Configure RIP.

# On the top navigation bar, click Network.

# From the navigation pane, select Routing > RIP. The RIP configuration page opens, as shown in Figure 4.

Figure 3 RIP configuration page

 

# Click Create.

# In the dialog box that opens, configure the RIP instance as shown in Figure 5. Add the configured static route and the direct network of the R&D department as redistributed routes.

Figure 4 Creating a RIP instance

 

# Click OK. The RIP instance is created, as shown in Figure 6.

Figure 5 RIP instance

 

Configuring Device B

1.     Assign IP addresses to interfaces and add the interfaces to security zones.

# On the top navigation bar, click Network.

# From the navigation pane, select Interface Configuration > Interfaces.

# Click the Edit icon for GE 1/0/1.

# In the dialog box that opens, configure the interface:

a.     On the Basic Configuration tab, select the Untrust security zone.

b.     On the IPv4 Address tab, enter the IP address and mask of the interface. In this example, enter 10.0.0.2/24.

c.     Click OK.

# Add GE 1/0/2 to the Trust security zone and set its IP address to 10.2.2.1/24 in the same way you configure GE 1/0/1.

2.     Create security policies.

# On the top navigation bar, click Policies.

# From the navigation pane, select Security Policies > Security Policies.

# Select Create > Create a policy.

# In the dialog box that opens, configure security policy rip-a:

a.     Enter policy name rip-a.

b.     Select source zone Trust.

c.     Select destination zone Untrust.

d.     Select type IPv4.

e.     Select action Permit.

f.     Enter source IPv4 address 10.2.2.0/24.

g.     Click OK.

# Configure security policy rip-b:

a.     Enter policy name rip-b.

b.     Select source zone Local.

c.     Select destination zone Untrust.

d.     Select type IPv4.

e.     Select service object group rip.

f.     Select action Permit.

g.     Click OK.

# Configure security policy rip-c:

a.     Enter policy name rip-c.

b.     Select source zone Untrust.

c.     Select destination zone Local.

d.     Select type IPv4.

e.     Select action Permit.

f.     Select service object group rip.

g.     Click OK.

3.     Configure RIP.

# On the top navigation bar, click Network.

# From the navigation pane, select Routing > RIP. The RIP configuration page opens, as shown in Figure 8.

Figure 6 RIP configuration page

 

# Click Create.

# In the dialog box that opens, configure the RIP instance as shown in Figure 9. Add the direct network of the financial department as a redistributed route.

Figure 7 Creating a RIP instance

 

# Click OK. The RIP instance is created, as shown in Figure 10.

Figure 8 RIP instance

 

Verifying the configuration

1.     Display the RIP routing table of Device A.

# On the top navigation bar, click Network.

# From the navigation pane, select Routing > Routing Table. The routing table is displayed, as shown in Figure 11.

Figure 9 Displaying the RIP routing table of Device A

 

2.     Display the RIP routing table of Device B.

# On the top navigation bar, click Network.

# From the navigation pane, select Routing > Routing Table. The routing table is displayed, as shown in Figure 12.

Figure 10 Displaying the RIP routing table of Device B

 

3.     Ping the gateway address 200.2.2.254 of the ISP on Device A.

<Device A> ping -a 10.1.1.1 200.2.2.254

Ping 200.2.2.254 (200.2.2.254) from 10.1.1.1: 56 data bytes, press CTRL_C to break

56 bytes from 200.2.2.254: icmp_seq=0 ttl=254 time=0.423 ms

56 bytes from 200.2.2.254: icmp_seq=1 ttl=254 time=0.222 ms

56 bytes from 200.2.2.254: icmp_seq=2 ttl=254 time=0.173 ms

56 bytes from 200.2.2.254: icmp_seq=3 ttl=254 time=0.170 ms

56 bytes from 200.2.2.254: icmp_seq=4 ttl=254 time=0.167 ms

 

--- Ping statistics for 200.2.2.254 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.167/0.231/0.423/0.098 ms

The output shows that the gateway can be pinged.

4.     Ping the gateway address 200.2.2.254 of the ISP on Device B.

<Device B> ping -a 10.0.0.2 200.2.2.254

Ping 200.2.2.254 (200.2.2.254) from 10.0.0.2: 56 data bytes, press CTRL_C to break

56 bytes from 200.2.2.254: icmp_seq=0 ttl=254 time=0.437 ms

56 bytes from 200.2.2.254: icmp_seq=1 ttl=254 time=0.209 ms

56 bytes from 200.2.2.254: icmp_seq=2 ttl=254 time=0.194 ms

56 bytes from 200.2.2.254: icmp_seq=3 ttl=254 time=0.174 ms

56 bytes from 200.2.2.254: icmp_seq=4 ttl=254 time=0.179 ms

 

--- Ping statistics for 200.2.2.254 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.174/0.239/0.437/0.100 ms

The output shows that the gateway can be pinged.