From: CCIEn2002 (ccie2002@xxxxxxxxxxxxx)
Date: Tue May 14 2002 - 01:07:52 GMT-3
All:
Thank you for all your help. I added the frame relay fragment
statement in my map class statement and everything is
good to go.. I see my ospf routes and my dlsw peers.
I am going to read about the frame relay fragment statement
more. Thank you all for the web links.
Thank you all
David
----- Original Message -----
From: <Dan.Thorson@seagate.com>
To: "Bill Hill" <bhill@sgdata.com>
Cc: <ccie2002@bellsouth.net>; <ccielab@groupstudy.com>
Sent: Monday, May 13, 2002 4:31 PM
Subject: RE: Vofr help on Cisco2610 and Cisco3620
>
> Unfortunately IP fragmentation on Frame Relay is not compatible with VoFR
> fragmentation.... FRF.11 vs. FRF.12. See the following on Cisco's www
> site:
> http://www.cisco.com/warp/public/788/vofr/fr_frag.html
>
> "A Frame Relay DLCI runs either FRF.12 or FRF.11. Never both, as they are
> mutually exclusive.
> o) If the DLCI is configured for VoFR, it uses FRF.11. If fragmentation is
> turned on for this DLCI, it uses FRF.11 Annex-C (or the Cisco derivative)
> for the fragmentation headers.
> o) If the DLCI is not configured for VoFR, it uses FRF.3.1 data
> encapsulation. If fragmentation is turned on for this DLCI, it uses FRF.12
> for the fragmentation headers. DLCIs carrying VoIP use FRF.12
fragmentation
> because VoIP is a layer 3 technology that is transparent to layer 2 Frame
> Relay."
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:55 GMT-3