From: Rick (fredricklowery@hotmail.com)
Date: Mon Apr 07 2003 - 21:54:00 GMT-3
Tim,
I took out the ip mtu 80 and it came right up. You are the man!
The fix to the original problem was to have FRTS on both sides
configured.
Thanks,
Rick
-----Original Message-----
From: Tim Fletcher [mailto:tim@fletchmail.net]
Sent: Monday, April 07, 2003 2:28 PM
To: fredricklowery@hotmail.com
Subject: RE: FRTS / OSPF problem
Try taking the ip mtu 80 out of the interface config. FRF is layer 2 and
should be completely transparent to IP. You might also try a bigger
fragment size. I've never used one as small as 80. Try 320 and see if
that
works, I know I had that working on a production network about a year
ago.
One good diagnostic tool for this is an extended ping. When it asks
"Extended commands" answer yes, and when you get to "Sweep range of
sizes"
say yes. You can accept all the defaults after that. This sends a series
of
pings, each one increasing in size. If you have FRF only configured on
one
side, your pings will start out as successful, but the minute they get
larger than your fragmentation size they will fail. If you have it
configured correctly, all the pings should be successful.
-Tim Fletcher #11406
At 01:52 PM 4/7/2003 -0400, you wrote:
>Tim,
>
>That still did not fix it. Here are the configs of the two routers that
>are sharing the p-2-p link.
>
>
>version 12.2
>no service single-slot-reload-enable
>service timestamps debug uptime
>service timestamps log uptime
>no service password-encryption
>!
>hostname r2
>!
>logging rate-limit console 10 except errors
>!
>ip subnet-zero
>no ip finger
>ip tcp synwait-time 5
>no ip domain-lookup
>!
>no ip dhcp-client network-discovery
>!
>!
>!
>!
>interface Loopback0
> ip address 200.0.0.2 255.255.255.255
>!
>interface Ethernet0
> ip address 150.50.17.2 255.255.255.0
>!
>interface Serial0
> no ip address
> encapsulation frame-relay
> frame-relay traffic-shaping
> frame-relay lmi-type ansi
>!
>interface Serial0.24 point-to-point
> ip address 150.50.24.2 255.255.255.0
> ip mtu 80
> ip policy route-map choose_r5
> frame-relay interface-dlci 104
> class voip
>!
>interface Serial0.256 multipoint
> ip address 150.50.100.2 255.255.255.224
> frame-relay map ip 150.50.100.2 105
> frame-relay map ip 150.50.100.5 105 broadcast
> frame-relay map ip 150.50.100.6 106 broadcast
>!
>interface Serial1
> no ip address
> shutdown
>!
>interface BRI0
> ip address 150.50.9.2 255.255.255.192
> shutdown
> isdn x25 static-tei 0
> cdapi buffers regular 0
> cdapi buffers raw 0
> cdapi buffers large 0
>!
>router ospf 1
> log-adjacency-changes
> network 150.50.9.0 0.0.0.63 area 0
> network 150.50.17.0 0.0.0.255 area 3
> network 150.50.24.0 0.0.0.255 area 1
> network 150.50.100.0 0.0.0.31 area 0
> network 200.0.0.2 0.0.0.0 area 0
> neighbor 150.50.100.6
> neighbor 150.50.100.5
>!
>ip kerberos source-interface any
>ip classless
>ip http server
>!
>!
>map-class frame-relay voip
> frame-relay cir 64000
> frame-relay bc 8000
> frame-relay mincir 64000
> no frame-relay adaptive-shaping
> frame-relay fair-queue
> frame-relay fragment 80
>access-list 100 permit ip any host 200.0.0.7 precedence critical
>route-map choose_r5 permit 10
> match ip address 100
> set ip next-hop 150.50.100.5
>!
>route-map choose-r5 permit 20
>!
>!
>alias exec srb sh run | begin
>alias exec sri sh run | include
> --More--
>02:12:33: %OSPF-5-ADJCHG: Process 1, Nbr 200.0.0.4 on Serial0.24 from
>EXSTART to DOWN, Neighbor Down: Too many DBD retransmitions
>!
>line con 0
> exec-timeout 0 0
> password cisco
> logging synchronous
> transport input none
>line aux 0
> exec-timeout 0 0
> logging synchronous
>line vty 0 4
> exec-timeout 0 0
> password cisco
> logging synchronous
> login
>!
>end
>
>r2#ter
>r2#terminal len
>r2#terminal length 0
>r2#sh run
>Building configuration...
>
>Current configuration : 2117 bytes
>!
>version 12.2
>no service single-slot-reload-enable
>service timestamps debug uptime
>service timestamps log uptime
>no service password-encryption
>!
>hostname r2
>!
>logging rate-limit console 10 except errors
>!
>ip subnet-zero
>no ip finger
>ip tcp synwait-time 5
>no ip domain-lookup
>!
>no ip dhcp-client network-discovery
>!
>!
>!
>!
>interface Loopback0
> ip address 200.0.0.2 255.255.255.255
>!
>interface Ethernet0
> ip address 150.50.17.2 255.255.255.0
>!
>interface Serial0
> no ip address
> encapsulation frame-relay
> frame-relay traffic-shaping
> frame-relay lmi-type ansi
>!
>interface Serial0.24 point-to-point
> ip address 150.50.24.2 255.255.255.0
> ip mtu 80
> ip policy route-map choose_r5
> frame-relay interface-dlci 104
> class voip
>!
>interface Serial0.256 multipoint
> ip address 150.50.100.2 255.255.255.224
> frame-relay map ip 150.50.100.2 105
> frame-relay map ip 150.50.100.5 105 broadcast
> frame-relay map ip 150.50.100.6 106 broadcast
>!
>interface Serial1
> no ip address
> shutdown
>!
>interface BRI0
> ip address 150.50.9.2 255.255.255.192
> shutdown
> isdn x25 static-tei 0
> cdapi buffers regular 0
> cdapi buffers raw 0
> cdapi buffers large 0
>!
>router ospf 1
> log-adjacency-changes
> network 150.50.9.0 0.0.0.63 area 0
> network 150.50.17.0 0.0.0.255 area 3
> network 150.50.24.0 0.0.0.255 area 1
> network 150.50.100.0 0.0.0.31 area 0
> network 200.0.0.2 0.0.0.0 area 0
> neighbor 150.50.100.6
> neighbor 150.50.100.5
>!
>ip kerberos source-interface any
>ip classless
>ip http server
>!
>!
>map-class frame-relay voip
> frame-relay cir 64000
> frame-relay bc 8000
> frame-relay mincir 64000
> no frame-relay adaptive-shaping
> frame-relay fair-queue
> frame-relay fragment 80
>access-list 100 permit ip any host 200.0.0.7 precedence critical
>route-map choose_r5 permit 10
> match ip address 100
> set ip next-hop 150.50.100.5
>!
>route-map choose-r5 permit 20
>!
>!
>alias exec srb sh run | begin
>alias exec sri sh run | include
>!
>line con 0
> exec-timeout 0 0
> password cisco
> logging synchronous
> transport input none
>line aux 0
> exec-timeout 0 0
> logging synchronous
>line vty 0 4
> exec-timeout 0 0
> password cisco
> logging synchronous
> login
>!
>end
>
>
>Current configuration : 1564 bytes
>!
>version 12.2
>service timestamps debug uptime
>service timestamps log uptime
>no service password-encryption
>!
>hostname r4
>!
>logging queue-limit 100
>!
>ip subnet-zero
>!
>!
>ip tcp synwait-time 5
>no ip domain-lookup
>!
>ip audit notify log
>ip audit po max-events 100
>!
>call rsvp-sync
>!
>!
>!
>!
>!
>!
>!
>!
>interface Loopback0
> ip address 200.0.0.4 255.255.255.255
>!
>interface Ethernet0/0
> ip address 10.1.1.4 255.255.255.0
> shutdown
> half-duplex
>!
>interface Serial0/0
> ip address 150.50.24.4 255.255.255.0
> encapsulation frame-relay
> ip ospf network point-to-point
> frame-relay traffic-shaping
> frame-relay map ip 150.50.24.2 401 broadcast
> frame-relay map ip 150.50.24.4 401 broadcast
> frame-relay interface-dlci 401
> class voip
> no frame-relay inverse-arp
> frame-relay lmi-type ansi
>!
>interface Ethernet0/1
> ip address 10.1.1.4 255.255.255.0
> half-duplex
>!
>interface Serial0/1
> no ip address
> encapsulation frame-relay
> shutdown
> frame-relay lmi-type cisco
>!
>router ospf 1
> log-adjacency-changes
> redistribute connected subnets
> network 150.50.24.0 0.0.0.255 area 1
>!
>ip classless
>ip http server
>!
>!
>map-class frame-relay voip
> frame-relay cir 64000
> frame-relay bc 8000
> frame-relay mincir 64000
> no frame-relay adaptive-shaping
> frame-relay fair-queue
> frame-relay fragment 80
>!
>!
>dial-peer cor custom
>!
>!
>!
>!
>alias exec srb sh run | begin
>alias exec sri sh run | include
>!
>line con 0
> exec-timeout 0 0
> password cisco
> logging synchronous
>line aux 0
> exec-timeout 0 0
> logging synchronous
>line vty 0 4
> exec-timeout 0 0
> password cisco
> logging synchronous
> login
>!
>end
>
>-----Original Message-----
>From: Tim Fletcher [mailto:tim@fletchmail.net]
>Sent: Monday, April 07, 2003 1:09 PM
>To: fredricklowery@hotmail.com
>Subject: RE: FRTS / OSPF problem
>
>Yes you do. It is a layer 2 fragmentation, not layer 3, so it has to be
>re-assembled on the other end of the link.
>
>At 11:49 AM 4/7/2003 -0400, you wrote:
> >Tim,
> >
> >I'm not sure what you mean. Are you saying that I have to do FRTS on
> >both sides? I appreciate you help through this tough issue.
> >
> >
> >Thanks,
> >Rick
> >
> >-----Original Message-----
> >From: Tim Fletcher [mailto:tim@fletchmail.net]
> >Sent: Monday, April 07, 2003 10:08 AM
> >To: Rick; ccielab@groupstudy.com
> >Cc: Rick
> >Subject: Re: FRTS / OSPF problem
> >
> >Rick,
> >
> >Do you have fragmentation set the same on both ends? If not, no
packets
> >larger than your fragment size will go through.
> >
> >-Tim Fletcher #11406
> >
> >At 06:58 PM 4/6/2003 -0400, Rick wrote:
> > >Can anyone please explain why the below FRTS config killed OSPF?
>After
> >I
> > >applied the traffic shapping commands the ospf neighbor exchange
was
> >hung.
> > >After I removed the below commands OSPF came right up
> > >Also, where on the DOC CD besides the WAN networking guide for
> >Frame-relay can
> > >I find some good FRTS information? Does anyone have any good
personal
> >notes on
> > >FRTS?
> > >
> > >Thanks,
> > >Rick
> > >
> > >
> > >r4#sh ip ospf neighbor
> > >
> > >Neighbor ID Pri State Dead Time Address
> >Interface
> > >200.0.0.2 1 EXCHANGE/ - 00:00:31 150.50.24.2
> >Serial0/0
> > >
> > >r4(config)#int s0/0
> > >r4(config-if)#no frame-relay class voip
> > >r4(config-if)#no frame-relay traffic-shaping
> > >r4(config-if)#end
> > >r4#
> > >r4#
> > >r4#
> > >r4#
> > >02:52:42: %OSPF-5-ADJCHG: Process 1, Nbr 200.0.0.2 on Serial0/0
from
> >LOADING
> > >to FULL, Loading Done
> > >
> > >Here is the config below.
> > >
> > >version 12.2
> > >service timestamps debug uptime
> > >service timestamps log uptime
> > >no service password-encryption
> > >!
> > >hostname r4
> > >!
> > >logging queue-limit 100
> > >!
> > >ip subnet-zero
> > >!
> > >!
> > >ip tcp synwait-time 5
> > >no ip domain-lookup
> > >!
> > >ip audit notify log
> > >ip audit po max-events 100
> > >!
> > >call rsvp-sync
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >interface Loopback0
> > > ip address 200.0.0.4 255.255.255.255
> > >!
> > >interface Ethernet0/0
> > > ip address 10.1.1.4 255.255.255.0
> > > shutdown
> > > half-duplex
> > >!
> > >interface Serial0/0
> > > ip address 150.50.24.4 255.255.255.0
> > > encapsulation frame-relay
> > > ip ospf network point-to-point
> > > frame-relay class voip
> > > frame-relay traffic-shaping
> > > frame-relay map ip 150.50.24.2 401 broadcast
> > > frame-relay map ip 150.50.24.4 401
> > > frame-relay lmi-type ansi
> > >!
> > >interface Ethernet0/1
> > > ip address 10.1.1.4 255.255.255.0
> > > half-duplex
> > >!
> > >interface Serial0/1
> > > ip address 150.50.24.4 255.255.255.0
> > > encapsulation frame-relay
> > > frame-relay map ip 150.50.24.2 401 broadcast
> > > frame-relay map ip 150.50.24.4 401
> > > frame-relay lmi-type cisco
> > >!
> > >router ospf 1
> > > log-adjacency-changes
> > > redistribute connected subnets
> > > network 150.50.24.0 0.0.0.255 area 1
> > >!
> > >ip classless
> > >ip http server
> > >!
> > >!
> > >map-class frame-relay voip
> > > frame-relay cir 64000
> > > frame-relay bc 640
> > > frame-relay mincir 64000
> > > no frame-relay adaptive-shaping
> > > frame-relay fair-queue
> > > frame-relay fragment 80
> > >!
> > >!
> > >dial-peer cor custom
> > >!
> > >!
> > >!
> > >!
> > >alias exec srb sh run | begin
> > >alias exec sri sh run | include
> > >!
> > >line con 0
> > > exec-timeout 0 0
> > > password cisco
> > > logging synchronous
> > >line aux 0
> > > exec-timeout 0 0
> > > logging synchronous
> > >
> > >
> > >Thanks,
> > >Rick
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:48 GMT-3