Re: 5-BRI fails intermittently
Jeff Vian (jvian@computer-services.com)
Tue, 04 Jun 1996 09:38:15 -0500
At 01:08 PM 6/3/96 -0600, you wrote:
>
>On Mon, 3 Jun 1996, Dave Carmean wrote:
>
>> Our 5-BRI card stops working every couple of days. Incoming
>> calls get "NO CARRIER". When I attach to one of the ports, and
>> try to dial back in, the first thing I see is a disconnect message, and
>> then nothing else. Rebooting the portmaster is the only way to get
>> it to work again. The lines are 5ESS P-T-P, and show good
>> status of "DCD- CTS+ TELCO+ NT1+".
>
>We have the same problem, but I haven't done much about it yet. Now is a
>good time. We have a PM2e with 20 async and 5-bri (the PM2e only version)
>running 3.3.1 on a 5ess ni-1 switch. The ports show "NO-SERVICE" and
>"DCD- CTS+ TELCO+ NT1+". This is supposed to mean "spid not registered",
>but the spid is correct, and when I called the telco to test it, they
>could see all the way to the nt1 with no problem. Rebooting fixes it. I
>haven't seen this happen for several days, but it had been happening two
>or three times a week.
>
>I have also noticed that other changes don't happen unless I reboot. For
>instance, if I:
>
>set s20 spid <invalid-number>
>reset s20
>
>People can still connect to s20. It doesn't complain about the invalid
>spid until I reboot.
>
>Could this be a problem with the pm2e-only 5-bri board? Dave, do your
>ports show "NO-SERVICE" when this happens? Does anyone else have this
>problem?
It's not the 2e only board.
I have a 2eR with the rev C board that does the same thing.
ComOs 3.3.1
The situation I have noted is that I have found problems using the BitSurfer
Pro to dial in to the PM. If it fails to make a connection and redials
several times in the attempt then the 5BRI appears to lock out the port.
The 'sh ses' says "NO SERVICE" but a 'sh s15' says idle with "DCD- CTS+
TELCO+ NT1+". The Telco says everything is working, including a loopback
through the NT1 on the 5BRI board.
Numeroous attempts to reset the port fail to reestablish service. As you
described the only way to restore service is to reboot.
I have called Livingston several times on this but as yet they fail to admit
it is a problem and blame it on the telco.
In another issue on the same board, I recently had port s15 go to sleep.
The incoming call appears to connect on both channels, but a 'sh ses' shows
s14 active and s15 idle.
I had the telco check everything out and they told me both channels were
connecting so I called tech support at Livingston.
They said this is a problem they had already seen and don't as yet have a fix.
-------signature--------
I'm not God,
I just perform his miracles.