First thing I would do is configure the frame relay correctly. You are using point-to-point commands, (frame-relay interface-dlci x) on a multipoint interface, which is the default if you don't subinterface and configure the sub as p-t-p.
Dave Shahram Esfahani wrote: > > I am encountering a strange problem that I'm hoping someone can help with. > I'm running a FR hub and spoke environment with RIP. My layer 2 is fine, > and I can ping all interfaces from the hub and spokes. Here's the > topology: > > Rtr A (hub) ------- Rtr B > ------- Rtr C > ------- Rtr D > > On the hub, I'm able to receive all of the spoke's RIP updates but I get a > Traceback error when the hub tries to broadcast it's routing table. Below > is some relevant information: > > termsrv#sh ip route > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter > area > * - candidate default, U - per-user static route, o - ODR > P - periodic downloaded static route > > Gateway of last resort is not set > > R 16.0.0.0/8 [120/1] via 192.168.100.3, 00:00:06, Serial0 > 3.0.0.0/24 is subnetted, 1 subnets > C 3.3.3.0 is directly connected, Loopback1 > R 64.0.0.0/8 [120/1] via 192.168.100.4, 00:00:21, Serial0 > 10.0.0.0/24 is subnetted, 1 subnets > C 10.10.0.0 is directly connected, Loopback0 > C 193.1.1.0/24 is directly connected, Ethernet0 > R 12.0.0.0/8 [120/1] via 192.168.100.2, 00:00:25, Serial0 > R 194.0.0.0/24 [120/1] via 192.168.100.2, 00:00:25, Serial0 > C 192.168.100.0/24 is directly connected, Serial0 > R 195.0.0.0/24 [120/1] via 192.168.100.3, 00:00:07, Serial0 > > Current configuration: > ! > version 12.0 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname termsrv > ! > ip subnet-zero > no ip domain-lookup > ! > partition flash 2 8 8 > ! > ! > ! > process-max-time 200 > ! > interface Loopback0 > ip address 10.10.0.1 255.255.255.0 > no ip directed-broadcast > ! > interface Loopback1 > ip address 3.3.3.3 255.255.255.0 > no ip directed-broadcast > ! > interface Ethernet0 > ip address 193.1.1.2 255.255.255.0 > no ip directed-broadcast > no keepalive > ! > interface Serial0 > bandwidth 115200 > ip address 192.168.100.1 255.255.255.0 > no ip directed-broadcast > encapsulation frame-relay > no ip mroute-cache > cdp enable > frame-relay interface-dlci 100 > frame-relay interface-dlci 110 > frame-relay interface-dlci 115 > frame-relay lmi-type ansi > ! > router rip > network 3.0.0.0 > network 192.168.100.0 > network 193.1.1.0 > ! > ip classless > no ip http server > ! > ! > line con 0 > logging synchronous > transport input none > line 1 16 > no exec > transport input all > line aux 0 > line vty 0 4 > login > ! > end > > termsrv#debug ip rip > RIP protocol debugging is on > termsrv# > 20:18:07: RIP: received v1 update from 192.168.100.3 on Serial0 > 20:18:07: 16.0.0.0 in 1 hops > 20:18:07: 192.168.100.0 in 1 hops > 20:18:07: 195.0.0.0 in 1 hops > 20:18:07: RIP: received v1 update from 192.168.100.3 on Serial0 > 20:18:07: 16.0.0.0 in 1 hops > 20:18:07: 192.168.100.0 in 1 hops > 20:18:07: 195.0.0.0 in 1 hops > 20:18:07: RIP: received v1 update from 192.168.100.3 on Serial0 > 20:18:07: 16.0.0.0 in 1 hops > 20:18:07: 192.168.100.0 in 1 hops > 20:18:07: 195.0.0.0 in 1 hops > 20:18:07: RIP: received v1 update from 192.168.100.3 on Serial0 > 20:18:07: 16.0.0.0 in 1 hops > 20:18:07: 192.168.100.0 in 1 hops > 20:18:07: 195.0.0.0 in 1 hops > termsrv# > 20:18:17: RIP: source 193.1.1.2, mask 255.255.255.0 > 20:18:17: -Traceback= 3EDB84 3EDF4C 3EE014 2BBF80 3F1A50 3F1F08 > 20:18:17: RIP: source 3.3.3.3, mask 255.255.255.0 > 20:18:17: -Traceback= 3EDB84 3EDF4C 3EE014 2BBF80 3F1A50 3F1F08 > 20:18:17: RIP: source 192.168.100.1, mask 255.255.255.0 > 20:18:17: -Traceback= 3EDB84 3EDF4C 3EE014 2BBF80 3F1A50 3F1F08 > termsrv# > 20:18:18: RIP: received v1 update from 192.168.100.4 on Serial0 > 20:18:18: 192.168.100.0 in 1 hops > 20:18:18: 64.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.4 on Serial0 > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 64.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.4 on Serial0 > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 64.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.4 on Serial0 > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 64.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.2 on Serial0 > 20:18:19: 12.0.0.0 in 1 hops > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 194.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.2 on Serial0 > 20:18:19: 12.0.0.0 in 1 hops > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 194.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.2 on Serial0 > 20:18:19: 12.0.0.0 in 1 hops > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 194.0.0.0 in 1 hops > 20:18:19: RIP: received v1 update from 192.168.100.2 on Serial0 > 20:18:19: 12.0.0.0 in 1 hops > 20:18:19: 192.168.100.0 in 1 hops > 20:18:19: 194.0.0.0 in 1 hops > > termsrv#sh ver > Cisco Internetwork Operating System Software > IOS (tm) 2500 Software (C2500-I-L), Version 12.0(5)T, RELEASE SOFTWARE > (fc1) > Copyright (c) 1986-1999 by cisco Systems, Inc. > Compiled Fri 23-Jul-99 03:14 by kpma > Image text-base: 0x0000144C, data-base: 0x006628B4 > > Any ideas? I've searched CCO and couldn't find a bug. I'm running > 12.0(5)T. > > Thanks, > Shahram -- David Madland Sr. Network Engineer CCIE# 2016 Qwest Communications Int. Inc. [EMAIL PROTECTED] 612-664-3367 "Emotion should reflect reason not guide it" Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=25935&t=25864 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
