On Tue, 30 Dec 1997, Adam Wills (Global 2000) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On Tue, 30 Dec 1997 david@sparks.net wrote:
>
> > We're bringing up some livingston PM3's on frame here in Maine, and have
> > encountered a very odd problem.
> >
> > be coming in from the CO. Both ends indicate the T1 is up and that the
> > frame parts seem to be fine. On rare occasion, I've seen the PM say it
> > could ping the cisco, but in no case could the cisco ping the PM.
> >
> > Anyone run into this before? Cisco and Livingston TS both blamed the
> > other side for the problem. Any ideas most appreciated!
> >
>
On the Cisco, make sure you set 'no cdp enable' on the sub interface to
the Livingston. Also, load ComOS 3.7.2 if your not running it already,
clears up many frame issues on the Livingston.
Sample cisco config for a livingston on the other end
interface Serial1/1.4 point-to-point
description JRWent
ip address 207.230.36.109 255.255.255.252
bandwidth 512
no cdp enable
frame-relay interface-dlci 21 IETF
And then on the livingston
jrwent-gw> sh w1
----------------------- Current Status - Port W1 -------------------------
Status: ESTABLISHED
Input: 517857327 Abort Errors: 27/1
Output: 2340304937 CRC Errors: 21
Pending: 0 Overrun Errors: 0
TX Errors: 0 Frame Errors: 3
Modem Status: DCD+ CTS+
Active Configuration Default Configuration
-------------------- ---------------------
Port Type: Netwrk Netwrk (Hardwired)
Line Speed: Ext 512K Ext Clock
Modem Control: off off
Local Address: 207.230.36.110 207.230.36.110
Netmask: 255.255.255.252 255.255.255.252
Interface: frmW1 (FRM,Routing) (FRM,Routing)
Mtu: 1500 1500
Dial Group: 0
Annex-D Poll: 10 (seconds)
Old DLCI List: 18:207.230.36.109
> Typical arm-chair quarterbacking from the tech support sides :) I had
> this problem, it was in the livingston equipement. Set the debug on the
> livingston, and specifcally WATCH the frame SEQUENCE #'s. If you see
> them out of order, or missing etc, then thats your problem. They
> (livginston/lucent) supposedly FIXED this in the 3.7 COMos updates but I
> reproduced it on the pm2er's myself with their supposedly FIXED code. We
> just slapped a cisco on both ends and fixed the problem.
>
> I have never heard of this with a pm3 though, thats suprising to me.
> Also, the reason we saw the problem on the pm2er's was due to heavy use on
> a t1 circuit, about 60% capacity at peak overloaded it :) Again, thats
> all what i got from tech support about a year ago, but we havent used
> livingston for ROUTERS in ages (cisco 100%).
>
Livingston claims the 2eR can't handle a full T1 at full bore, so figures.
> I would check your SEQ #'s in the debug and see if you are really getting
> them properly received by the Livingston unit.
==============================================================
Tim Flavin Internet Access for St Louis & Chicago
Internet 1st, Inc Toll Free Sales & Support 800-875-3173
http://www.i1.net For more information email info@i1.net
==============================================================
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:14 EDT