I've seen exactly the same behavior here.
>> was increased. Note that we have other T1 cards which have not seen
>> the problem and a few which see it every few weeks.
Same here - however, my other T1 cards are running ppp, not frame-relay.
>I have also learned that the same problem can occur on a heavily loaded
circuit. >Essentially, the LMI packets can be discarded just like any other
packet, and the >result is a loss of LMI sync.
This, I did not know. Thanks for the info...
>I'd still like to be able to reset the problem without re-booting.
However, it is line2 which is stuck, not W48, and "reset line2" doesn't do
anything. Any ideas?
I currently have an open ticket with support on this issue... here's what
we've done so far:
Increased memory to 8 megs, since we're running OSPF and support
immediately suggested it could be memory related.
Also, I used one of the earlier PMVision versions to upgrade the box to
3.8.2. The WAN group suggested that I reload the ComOS image just in case
it had gotten slightly garbled during the initial upgrade (I did have two
boxes completely fail the upgrade with PMVision). I used tftp to load a
new copy of the 3.8.2 image.
Here's how things stand:
W48 - 216.46.38.18 Netwrk Hrd ESTABLISHED 2days 0
pm3-1.mgv> ver
Livingston PortMaster PM-3 ComOS 3.8.2
System uptime is 3 days 11 hours 13 minutes
pm3-1.mgv>
W48 only has an uptime of 2 days because I intentionally reset it while
working on OSPF issues.
So far, so good... we'll see who things go for the next few days before I
close the ticket, though.
Dave Stewart
System Manager
Homenet Communications, Inc.
=============================================
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>