From: OhioHondo (ohiohondo@columbus.rr.com)
Date: Mon Apr 07 2003 - 10:22:23 GMT-3
Good catch!!
Just a note -- If you are using fragmentation to resolve outbound
serialization delay, you probably need it for serialization delay in the
opposite direction (the other router) as well --- called egress
serialization delay because it is from the frame switches perspective. Even
if the remote router has a high Signaling Rate, the frame(s) (especially
large frames) have to be buffered at the frame switch for delivery at the
remote end. (i.e. a router with a T1 delivering to a router with a 64K)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
FATHALLAH
Sent: Monday, April 07, 2003 7:42 AM
To: Rick
Cc: Ccielab
Subject: RE: FRTS / OSPF problem
Hi,
According to ospf specification. the adjency don't get up if the two
neighbors use different IP MTU. the frame-relay fragment command change
indirectly the MTU and IP MTU of you frame interface. now instead of
removing this command witch make incomlete your FRTS config. try to make the
same fragment in the other hand of the frame-relay. if no FRTS is required
in the other router. try configuring ip mtu with the same fragement size.
IP MTU 80).
regards.
-----Message d'origine-----
De : nobody@groupstudy.com [mailto:nobody@groupstudy.com]De la part de
Rick
Envoyi : lundi 7 avril 2003 01:05
@ : premji@speakeasy.net
Cc : ccielab@groupstudy.com
Objet : Re: FRTS / OSPF problem
As a matter of fact it fixes the problem. Now, why is this? Thanks for you
help!
----- Original Message -----
From: <premji@speakeasy.net>
To: "Rick" <ccie_2003@hotmail.com>
Sent: Sunday, April 06, 2003 8:53 PM
Subject: Re: FRTS / OSPF problem
> does removing the fragment statement help ?
>
> -Ariff
>
> On Sun, 6 Apr 2003, 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