-----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!
>
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%).
I would check your SEQ #'s in the debug and see if you are really getting
them properly received by the Livingston unit.
Adam Wills Global 2000 Communications
Director of Networking Systems 1840 Western Ave.
sysadmin@global2000.net Albany, NY, 12203
http://www.global2000.net (518) 452-1465
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNKlsJK7yaLQI4biZAQFqbgP/Rfu4FXeNrYVBjOjNdnT4oYh07/BNtyRg
OPSKAm4e3j0qff3/a0bnAQ3lDsU+bzt5lcR7tHJVhwuxXEJR6b4+M+P5XEuFlilu
l6y0Ff1WqRucFSHeTXIMuuOVhgzlh9nyfNUd4ETlv2okaeD44GAc7hlEgOyTwONE
97YgqgdBPCg=
=7SAc
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:14 EDT