Case Study Configuring Unicast Updates
Next, router Bea is added to the Ethernet link that Andy and Floyd share (Figure 5.11). The no-RIP policy between Andy and Floyd remains in place, but now Bea and Andy, as well as Bea and Floyd, must exchange RIP advertisements.
Figure 5.11. No RIP updates should be exchanged between Andy and Floyd, but both should exchange updates with Bea.
192 1SB 12 6S/27
Figure 5.11. No RIP updates should be exchanged between Andy and Floyd, but both should exchange updates with Bea.
192 1SB 12 6S/27
Cotter Opbe
The configuration of Bea is straightforward:
router rip network 192.168.12.0 network 192.168.200.0
The addition of a neighborcommand under the RIP processes of Andy enables RIP to send a unicast advertisement to Bea's interface while the passive-interface command continues to prevent broadcast updates on the link.191
191 Another use of neighbor is to enable unicast updates on nonbroadcast media such as Frame Relay.
Andy's configuration is:
router rip passive-interface Ethernet0 network 172.17.0.0 network 192.168.12.0 network 192.168.83.0 neighbor 192.168.12.67
Because Floyd must now send advertisements to Bea, a network command for 192.168.12.0 must be added. Passive-interface is also added to prevent broadcast updates, and a neighbor command is added to enable unicast updates to Bea:
router rip passive-interface Ethernet0 network 192.168.12.0 network 192.168.100.0 neighbor 192.168.12.67
By enabling debug ip rip events at Andy, the results of the new configuration can be verified (Figure 5.12). Andy is receiving updates from Bea, but not from Floyd, and is sending updates directly to Bea's interface, but is not broadcasting on its E0.
Continue reading here: Operation of IGRP
Was this article helpful?