Hi All,
I have a question on the ip rip triggered updated command and need help.
I have two routers R1 and R2 connected via serial link with PPP
encapsulation.
I have manually assigned the IP address to the serial links and have
configured RIP with triggerd updates.
R1 information:
R1#sh ip int brief
Interface IP-Address OK? Method Status
Protocol
Serial0/0 10.60.0.1 YES NVRAM up
up
Serial0/1 unassigned YES NVRAM administratively down
down
Serial0/2 unassigned YES NVRAM administratively down
down
Serial0/3 unassigned YES NVRAM administratively down
down
Loopback0 172.11.1.1 YES NVRAM up
up
Loopback1 172.11.2.1 YES NVRAM up
up
Loopback2 172.11.3.1 YES NVRAM administratively down
down
R1#
R1#
R1#sh ip route rip
172.22.0.0/24 is subnetted, 3 subnets
R 172.22.2.0 [120/1] via 10.60.0.2, 00:01:46, Serial0/0
R 172.22.3.0 [120/1] via 10.60.0.2, 00:00:35, Serial0/0
R 172.22.1.0 [120/1] via 10.60.0.2, 00:01:46, Serial0/0
R1#
R1#
R1#sh ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 15 seconds
Invalid after 180 seconds, hold down 0, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0 2 2 Yes RIP-KEYS
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.11.0.0
Passive Interface(s):
Loopback0
Loopback1
Loopback2
Routing Information Sources:
Gateway Distance Last Update
10.60.0.2 120 00:00:43
Distance: (default is 120)
R2 Information
R2#sh ip int brief
Interface IP-Address OK? Method Status
Protocol
Serial0/0 10.60.0.2 YES manual up
up
Serial0/1 unassigned YES NVRAM administratively down
down
Serial0/2 unassigned YES NVRAM administratively down
down
Serial0/3 unassigned YES NVRAM administratively down
down
Loopback0 172.22.1.1 YES NVRAM up
up
Loopback1 172.22.2.1 YES NVRAM up
up
Loopback2 172.22.3.1 YES NVRAM up
up
R2#
R2#
R2#
R2#sh ip route rip
172.11.0.0/24 is subnetted, 3 subnets
R 172.11.3.0 [120/1] via 10.60.0.1, 00:00:14, Serial0/0
R 172.11.2.0 [120/1] via 10.60.0.1, 00:00:30, Serial0/0
R 172.11.1.0 [120/1] via 10.60.0.1, 00:00:30, Serial0/0
R2#
R2#
R2#
R2#sh ip pro
R2#sh ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 22 seconds
Invalid after 180 seconds, hold down 0, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0 2 2 Yes RIP-KEYS
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.22.0.0
Passive Interface(s):
Loopback0
Loopback1
Loopback2
Routing Information Sources:
Gateway Distance Last Update
10.60.0.1 120 00:00:18
Distance: (default is 120)
The triggered updated just work fine in this scenario. However, when I
configure R2 to negotiate the IP address from R1's local pool,
then triggered updates from R2 would not be sent to R1. R1 loses all the
routes from R2. R2 retains R1's routes and triggered updates from R1 is sent
to R2.
R2 output after IP address is negotiated via IPCP.
R2#sh ip int brief
Interface IP-Address OK? Method Status
Protocol
Serial0/0 10.60.0.4 YES IPCP up
up
Serial0/1 unassigned YES NVRAM administratively down
down
Serial0/2 unassigned YES NVRAM administratively down
down
Serial0/3 unassigned YES NVRAM administratively down
down
Loopback0 172.22.1.1 YES NVRAM up
up
Loopback1 172.22.2.1 YES NVRAM up
up
Loopback2 172.22.3.1 YES NVRAM up
up
R2#
R2#
R2#sh ip route rip
172.11.0.0/24 is subnetted, 3 subnets
R 172.11.3.0 [120/1] via 10.60.0.1, 00:00:32
R 172.11.2.0 [120/1] via 10.60.0.1, 00:00:32
R 172.11.1.0 [120/1] via 10.60.0.1, 00:00:32
R2#
R2#
R2#sh ip pro
R2#sh ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 14 seconds
Invalid after 180 seconds, hold down 0, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0 2 2 Yes RIP-KEYS
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.22.0.0
Passive Interface(s):
Loopback0
Loopback1
Loopback2
Routing Information Sources:
Gateway Distance Last Update
10.60.0.1 120 00:00:37
Distance: (default is 120)
R1's output after R2 is configured for ip address negotiation
R1#sh ip int brief
Interface IP-Address OK? Method Status
Protocol
Serial0/0 10.60.0.1 YES NVRAM up
up
Serial0/1 unassigned YES NVRAM administratively down
down
Serial0/2 unassigned YES NVRAM administratively down
down
Serial0/3 unassigned YES NVRAM administratively down
down
Loopback0 172.11.1.1 YES NVRAM up
up
Loopback1 172.11.2.1 YES NVRAM up
up
Loopback2 172.11.3.1 YES NVRAM up
up
R1#
R1#sh ip route rip
R1#
R1#
R1#
R1#sh ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 20 seconds
Invalid after 180 seconds, hold down 0, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0 2 2 Yes RIP-KEYS
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.11.0.0
Passive Interface(s):
Loopback0
Loopback1
Loopback2
Routing Information Sources:
Gateway Distance Last Update
10.60.0.2 120 00:06:16
Distance: (default is 120)
So is this working as designed? will the triggered updates from the
negotiated peer would not be sent to R1?
Any ideas would be very helpful.
regards,
sharath
