Welcome to part 3 of this series of video labs. Continuing on from Part 2 - Configuring Frame Relay. I'll now show you how to configure RIPv2 on the frame-relay network. If you've jumped into the series here and haven't seen the network topology, please check it out at the bottom of the page before going ahead.

Configuration Video:

Continuing on from part 2, the first thing we do is add some loopback interfaces to the routers:

R1(config)#interface loopback 0
R1(config-if)#ip address 1.1.1.1 255.255.255.0
R2(config)#interface loopback 0
R2(config-if)#ip address 2.2.2.2 255.255.255.0
R3(config)#interface loopback 0
R3(config-if)#ip address 3.3.3.3 255.255.255.0

The next thing we need to change is the frame-relay map statements from part 2. The reason we need to do this is RIP version 2 uses multicasts (224.0.0.9) to send its route advertisements. Frame relay treats multicasts the same way it does broadcasts, which means these wont be forwarded over the frame-relay network. In order to allow these packets to go over the network we need to modify the frame-relay map statements and appened the broadcast flag to the end.

R1(config-if)#interface serial 0/0
R1(config-if)#no frame-relay map ip 172.16.1.3 100
R1(config-if)#frame-relay map ip 172.16.1.3 100 broadcast
R2(config)#interface serial 0/0
R2(config-if)#no frame-relay map ip 172.16.1.3 200
R2(config-if)#frame-relay map ip 172.16.1.3 200 broadcast
R3(config)#interface serial 0/0
R3(config-if)#no frame-relay map ip 172.16.1.1 300
R3(config-if)#no frame-relay map ip 172.16.1.2 301
R3(config-if)#frame-relay map ip 172.16.1.1 300 broadcast
R3(config-if)#frame-relay map ip 172.16.1.2 301 broadcast

We only use the broadcast flag once on the stub routers since all the traffic goes through the hub, if we used the broadcast flag in both frame-relay map statements then we would be generating redudant broadcasts/multicasts.

Once we're done with the frame-relay map statements you can check them using the show frame-relay map command:

R3#show frame-relay map
Serial0/0 (up): ip 172.16.1.1 dlci 300(0x12C,0x48C0), static,
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 172.16.1.2 dlci 301(0x12D,0x48D0), static,
              broadcast,
              CISCO, status defined, active

You can use the show frame-relay pvc command to view frame-relay statistics and also the PVC status, which if all is well should be active:

R3#show frame-relay pvc

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

              Active     Inactive      Deleted       Static
  Local          2            0            0            0
  Switched       0            0            0            0
  Unused         0            0            0            0

DLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

  input pkts 0             output pkts 0            in bytes 0        
  out bytes 0              dropped pkts 0           in pkts dropped 0        
  out pkts dropped 0                out bytes dropped 0        
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0        
  out BECN pkts 0          in DE pkts 0             out DE pkts 0        
  out bcast pkts 0         out bcast bytes 0        
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:00:18, last time pvc status changed 00:00:18
         
DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

  input pkts 0             output pkts 0            in bytes 0        
  out bytes 0              dropped pkts 0           in pkts dropped 0        
  out pkts dropped 0                out bytes dropped 0        
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0        
  out BECN pkts 0          in DE pkts 0             out DE pkts 0        
  out bcast pkts 0         out bcast bytes 0        
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:00:14, last time pvc status changed 00:00:14

Before we move onto the RIP setup it's always good to test your connectivity. Next we'll configure RIP on our routers. We'll set RIP to send and receive version 2 updates only, and also disable auto summary. Last of all we'll set which networks we want to advertise using the network command.

R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#no auto-summary
R1(config-router)#network 172.16.0.0
R1(config-router)#network 1.0.0.0
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#no auto-summary
R2(config-router)#network 172.16.0.0
R2(config-router)#network 2.0.0.0
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#no auto-summary
R3(config-router)#network 172.16.0.0
R3(config-router)#network 3.0.0.0

That completes the RIP setup. We'll check the routing table using the show ip route command:

Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets
R       1.1.1.0 [120/1] via 172.16.1.1, 00:00:09, Serial0/0
     2.0.0.0/24 is subnetted, 1 subnets
R       2.2.2.0 [120/1] via 172.16.1.2, 00:00:10, Serial0/0
     3.0.0.0/24 is subnetted, 1 subnets
C       3.3.3.0 is directly connected, Loopback0
     172.16.0.0/24 is subnetted, 1 subnets
C       172.16.1.0 is directly connected, Serial0/0

Which shows the RIP advertised networks. Finally we'll test connectivity from the spoke routers to the RIP advertised loopback networks.

R1#ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/115/121 ms

R2#ping 1.1.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/116/124 ms

Success! Some other helpful commands you can use are the show ip protocols command, which will show you the RIP timers among other things.

R1#sh ip protocols
Routing Protocol is "rip"
  Sending updates every 30 seconds, next due in 13 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send  Recv  Triggered RIP  Key-chain
    Serial0/0             2     2                                   
    Loopback0             2     2                                   
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    1.0.0.0
    172.16.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    172.16.1.3           120      00:00:01
  Distance: (default is 120)

The sh ip rip database command will show the contents of the RIP database:

R1#sh ip rip database
1.0.0.0/8    auto-summary
1.1.1.0/24    directly connected, Loopback0
2.0.0.0/8    auto-summary
2.2.2.0/24
    [2] via 172.16.1.3, 00:00:24, Serial0/0
3.0.0.0/8    auto-summary
3.3.3.0/24
    [1] via 172.16.1.3, 00:00:24, Serial0/0
172.16.0.0/16    auto-summary
172.16.1.0/24    directly connected, Serial0/0