Here's one that worked for me. The other end is just a straight IETF
frame-relay config. Use the abr, ubr, etc. on the pvc to indicate the pvc
setting from your provider. Also watch out for "tagging" which affects how
the qos bits are mapped into the frame fecn becn scheme. We got bit by that.
Some pvc's needed it, others didn't. Make sure to do a throughput test to
check your settings. We had some wierd latency issues.
interface ATM1/0
no ip address
no ip mroute-cache
no atm ilmi-keepalive
interface ATM1/0.137 point-to-point
description PVC to Customer
bandwidth 128
ip address X.X.X.1 255.255.255.248
no ip mroute-cache
pvc ONE37 1/37
protocol ip X.X.X.2 broadcast
abr 128 128
inarp 1
protocol ip inarp
!
-----Original Message-----
From: Dan Hollis [mailto:goemon@anime.net]
Sent: Thursday, June 28, 2001 3:44 PM
To: cisco-nsp@puck.nether.net
Subject: [nsp] 3640 ATM to Frame Relay config?
Anyone have a sample config for ATM to Frame Relay?
3640:ATM - ATM:ILEC:FR - FR:3640
The 3640:ATM has NM-4T-IMA, ILEC assigned vpi/vci 4/47.
The 3640:FR has WIC-T1, ILEC assigned DLCI 17.
The ILEC is qwest.
I looked all over the cisco site for sample configs but they all appear to
be MC3810-specific configs, or configs for FR-to-ATM switching on the same
cisco, not ATM to FR over WAN on 36xx's.
The command 'encapsulation aal5mux frame-relay' that is repeatedly
referred to in cisco documentation does not seem to be available on
C3640-IS-M 12.1(6).
-Dan
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:43 EDT