From: Wade Edwards (wade.edwards@xxxxxxxxxxxxxxxxxxx)
Date: Thu Jun 27 2002 - 18:32:18 GMT-3
Looks like it was the frame relay encapsulation that was the problem. It
looks like it only works with IETF encapsulation and not Cisco. The
documentation does not state this fact and it took me a while to track
it down.
Thanks to all who answered for your input.
L8r.
-----Original Message-----
From: Frank Jimenez [mailto:franjime@cisco.com]
Sent: Thursday, June 27, 2002 10:40 AM
To: Wade Edwards; 'Ccielab (E-mail)'
Subject: RE: FRF.8
Feature navigator www.cisco.com/go/fn says that FRF.8 has been supported
on MC3810s since 12.1.2(T) in the T train and 12.2.1 in mainline code.
Might want to get a case open with TAC to see if they know of specific
gotchas. Barring that, I might try 12.2(8)T4 - I've had lots of good
luck with that code on oddball problems....
Good Luck!
Frank Jimenez, CCIE #5738
franjime@cisco.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Wade Edwards
Sent: Thursday, June 27, 2002 9:53 AM
To: Ccielab (E-mail)
Subject: OT: FRF.8
Sorry for the off topic post but I am having problems getting FRF.8
(Frame-to-ATM) working on an MC3810.
I can get packets to be converted from ATM-to-Frame but the other
direction is not working. Has anyone else been able to get this working?
I know the problem is with the MC3810 because I get Frame traffic
inbound but I don't get any outbound traffic on the ATM interface.
I have tried another MC3810 and various IOS versions but no go.
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:42 GMT-3