You are definitely having problems here.
The proper cables required for PRI ISDN have RJ48 connectors (not RJ45)
They look the same, the only difference I have noticed is that they are STP
instead of UTP.
I would get yourself some Shielded Twisted pair cable for the PRI.
Did you do a save all before you switched off each PM.
If you loose config for no apparent reason, I would erase all the flash and
reload the ComOS and config anew. Corrupted Flash memory can cause all sorts
of problems.
This sometimes points to tired Flash memory, which then needs replacing.
Good Luck
James
P.S. You have been very unlucky, resiting a PM box should not cause any
problem.
> -----Original Message-----
> From: owner-portmaster-users@livingston.com
> [mailto:owner-portmaster-users@livingston.com]On Behalf Of Scott Bethke
> Sent: Monday, April 05, 1999 05:03
> To: portmaster-users@livingston.com
> Subject: (PM) strange problem w/ pm3
>
>
>
> Im having a new strange problem with my pm3's, wondering if anyone has had
> this happen. By the way Bravo! to livingston's tech support!! I called
> and got a tech right away, no waiting for a return call, and they guy knew
> what he was doing. I have to say it is by far the BEST service I've got
> from any tech support place in a long while.
>
> Anyway.. here we go. Our PM3's have been happily running along fine till
> Friday night. We decided to move all of our pm3's closer to the telco
> rack. So we take them off line, move them over and use new cables to
> connect to the PRI's. All seem to come up fine and start working. We
> notice that tech support is getting an average of 3 to 4 calls every 15
> minutes with people who can't connect. We get on the first pm3 and notice
> that all of our OSPF settings are gone (Strange but no problem,
> we just put
> them back in) OSPF stuff is still in all of our remaining PM3's. We check
> the Radius logs and notice that users on the first two pm3's are login in
> with garbage like this:
>
> Apr 5 10:50:08 auth.ezy.net radius[17920]: auth: access-request from
> 206.43.209.53/1026.59 denied for unknown user
> ")LfiS$dx9vm*|~?-:r<Oy4}x1~?~?~?~?~?~?%" at 4107XXX389
> Apr 5 10:50:09 auth.ezy.net radius[17921]: auth: access-request from
> 206.43.209.53/1026.60 denied for unknown user "4):xn&*" at 4107XXX389
> Apr 5 10:51:35 auth.ezy.net radius[17933]: auth: access-request from
> 206.43.209.6/1026.163 denied for unknown user "tmt})o
> U@d}=@*O.}iXR%iVQ" at
> 4103XXX741
>
> Not everyone, just certain people. The box is full of people who seem to
> work fine. sh line1 and sh line0 say our PRI's are running fine (no crc's
> etc). Now we have seen this before when people have odd modems, or older
> kflex code, or other stupid "modem" problems but this is different. It's
> happening to people who worked fine before we moved the pm3's.
>
> tech support has a ticket on this, I was hoping that some of you had been
> through this before and had a solution. We have swapped the
> cables for new
> my next step was going to be to re-install an older or newer COMOS to get
> the modems re flashed?? does that sound like a good thing to try?
>
> -Scott
>
> -
> 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/>