Re: (PM) Up and down PRI, errors, show ISDN questions

Vernon Burke (vburke@skow.net)
Thu, 4 Feb 1999 14:26:55 -0000

Line tests or reading the error log out of the pairgain box
should be all the proof required. It's 100% certain that they
did a lousy splicing job on the cable pairs.

Vern

----- Original Message -----
From: Billy Hamblin <billyh@midsouth.net>
To: <portmaster-users@livingston.com>
Sent: Thursday, February 04, 1999 9:23 PM
Subject: (PM) Up and down PRI, errors, show ISDN questions

>We are having a great streak of luck here. We swapped over to ComOS 3.8.2 a
>week and a half ago with no visible improvement. We haven't lost a customer
>yet....but I have about 5-10 customers that are right on the edge. Now this
>Monday we have all our PRI and our T-1s cut physically at the pole. Bell
>South was suprisingly responsive and got the lines back up that night. Well
>ever since then all hell has broke loose. We were up for a few hours at
>most. I got dropped from home and couldn't reconnect. Once I got to the
>office all the PM's were down. To be more specific I had maybe handful of
>users on when they should have been full. The people who were on were idle
>for the most part. I noticed intermintant error lights on our pairgain
>boxes(PRI+T-1s). I tried getting in to the Pms via PMvision and telnet and
>after rebooting the machines I could get in but I was having trouble
>keeping a connection to them. We finally got everything stable the next
>morning but they seem to be going down twice a day in about 12 hour
>intervals. We have NEVER had a problem like this with out PRI before. I
>want to think that Bell gave us a crappy patch job on the lines. I guess we
>have been spoiled by the fact we never had a problem before and therefore
>I'm not sure how to proceed in showing Bell the lines are bad. I've looked
>at the line0,1 on each PM and I'll attach that below. I also did a sh isdn
>and thats included as well. I've rarely had the need other than curiosity
>to look at these before but I know we did not have these kinds of errors
>showing and thats when the Pms were up for 30+ days at a time. We are
>getting these errors in the course of a day or two. My other question is
>could it be possible that when the lines were severed the Pms could have
>suffered any damage in the ethernet port or other areas?
>
>pm1> sh isdn
>D Ports State L1 L2 Change init Up Down
>-- ------- ------------- ------- ----- ----- -----
> 0 S0-S22 UP Active 2 7 1 6
> 1 S24-S46 UP Active 2 7 1 6
>
>---------------------- line0 - T1 Primary Rate ISDN ---------------
>
> Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
>
> Receive Level: +2dB to -7.5dB
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 1 CRC Errors 0
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync 0
>
>---------------------- line1 - T1 Primary Rate ISDN ---------------
>
> Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
>
> Receive Level: +2dB to -7.5dB
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 1 CRC Errors 0
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync
>
>
>
>
>
>
>D Ports State L1 L2 Change init Up Down
>-- ------- ------------- ------- ----- ----- -----
> 0 S0-S22 UP Active 0 7 1 6
> 1 S24-S46 UP Active 0 7 1 6
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 1 CRC Errors 0
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync 0
>
>PM#2> sh line1
>---------------------- line1 - T1 Primary Rate ISDN ---------------
>
> Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
>
> Receive Level: +2dB to -7.5dB
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 1 CRC Errors 7
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync 0
>
>
>PM#3> sh isdn
>D Ports State L1 L2 Change init Up Down
>-- ------- ------------- ------- ----- ----- -----
> 0 S0-S22 UP Active 4 6 1 5
> 1 S24-S46 DOWN Inactive 5 0 0 0
>PM#3>
>PM#3> sh line0
>---------------------- line0 - T1 Primary Rate ISDN ---------------
>
> Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
>
> Receive Level: +2dB to -7.5dB
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 1 CRC Errors 0
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync 0
>
>The 3rd Pm only has one PRI thus far. Any help or advice based on the
>errors shown would be appreciated. The natives here are restless!
>Thanks
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|Billy Hamblin - Residential OM |
>|Midsouth ConNEcTions - 931.648.9024 |
>|1770-B Madison St. - billyh@midsouth.net |
>|Clarksville Tn 37043 |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>-
>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/>