Re: (PM) BRI no-service on PM2e

Krzysztof Adamski (kadamski@netsurf.net)
Sat, 18 Jul 1998 11:37:17 -0400 (EDT)

I have a bunch of OR's with customers, I have not upgraded the ComOS on
them so it's a mixed bag of versions. The one that is most stable is this
one:

awtbo> ver
Livingston Enterprises PortMaster Version 3.4.2L
System uptime is 501 days 3 hours 7 minutes

The line has not been up this long, but it has never had any problems
related with the line.

Here is an other that is located 2 building down on the same street:
hnoisdn> ver
Livingston PortMaster Office Router ComOS 3.5L
System uptime is 138 days 1 hours 22 minutes

A third one, again three buildings down on the same street:
ballisdn> ver
Livingston PortMaster Office Router ComOS 3.5L
System uptime is 23 days 5 hours 3 minutes

What does this prove, I don't know, only that 3.4.2L was a VERY stable
version of ComOS. But if you want OSPF then you have to use something
else.

K

On Sat, 18 Jul 1998, Roy wrote:

> There seems to be a known bug in the 3.7.2 release where the D channel
> hangs in the F6 state. Rebooting doesn't help! Only thing I have found
> that works remotely is to have the telco run a line check!
>
> Still waiting for Livingston to fix it
>
> Krzysztof Adamski wrote:
> >
> > One more way is to unplug the BRI and plug it back, yes I know this sounds
> > silly, but I have found that sometimes this works when reseting the D does
> > not.
> >
> > K
> >
> > On Fri, 17 Jul 1998, Jon Lewis wrote:
> >
> > > On Thu, 16 Jul 1998, Todd M. Jagger wrote:
> > >
> > > > 3.7.2) at another POP. This afternoon I noticed that one of the ports for
> > > > this connection on the PM2e has gone into NO-SERVICE. I've read through
> > > > the threads on this here and it seems that the only solution is to reboot
> > > > the PM2e? Is this the _only_ way to take the port out of this state?
> > > >
> > > > I've tried resetting the ports, rebooting the ORU, etc. but didn't do the
> > > > trick. I'll have to wait until much later tonight to reboot the PM2e when
> > > > there are less users on the system.
> > >
> > > If a BRI on the PM2 is in NO-SERVICE, why would you reboot the OR-U?
> > > Sometimes when this happens, resetting the D channel will help (far more
> > > often than resetting the S channels), but sometimes a reboot is the only
> > > solution. I've been told re-entering the spids and dirnums can help...but
> > > in my case I don't think it ever did.
> > >
> > >
> > > ------------------------------------------------------------------
> > > Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or
> > > Network Administrator | drawn and quartered...whichever
> > > Florida Digital Turnpike | is more convenient.
> > > ______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
> > >
> > > -
> > > 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/>
> > >
> >
> > -
> > 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/>
>

-
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/>