Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Phone system just died and came back what happened?

Status
Not open for further replies.

Future00

Technical User
Nov 18, 2004
174
US
Our Opt 81c Succession 3 just went down briefly and came back up. Here is what I caught in the terminal. What does it look like happened?

Thanks

===========================================================

TIM454 15:00 23/5/2005 CPU 1

TTY #05 LOGGED OUT ADMIN2 15:18 23/5/2005
SESSION DURATION: 00:50

AUD000

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR011 NET 24 S 7

XMI000 24 : RSIG link lost - Reinitialized

FIR009 NET 24 S

FIR010 NET 24 S

FIR015 NET 24 S

FIR003 NET 24

FIR015 NET 24 S

FIR110 PEC 5 P

FIR104 PEC 5 P

FIR004 NET 24

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR003 NET 24

FIR015 NET 24 S

FIR110 PEC 5 P

FIR012 NET 24

FIR104 PEC 5 P

FIR004 NET 24

XMI000 24 : RSIG link lost - Reinitialized

FIR009 NET 24 S

FIR010 NET 24 S

FIR015 NET 24 S

FIR104 PEC 5 P

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR003 NET 24

FIR015 NET 24 S

FIR004 NET 24

XMI000 24 : RSIG link lost - Reinitialized

FIR009 NET 24 S

FIR010 NET 24 S

FIR015 NET 24 S

FIR104 PEC 5 P

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR003 NET 24

FIR015 NET 24 S

FIR110 PEC 5 P

FIR111 PEC 5 P 8

FIR104 PEC 5 P

FIR004 NET 24

XMI000 24 : RSIG link lost - Reinitialized

FIR009 NET 24 S

FIR010 NET 24 S

FIR015 NET 24 S

FIR011 NET 24 S 8

FIR104 PEC 5 P

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR112 PEC 5

FIR115 PEC 5 P

XMI000 24 : Msg from FPEC error #0001

XMI000 24 : Msg from FPEC error #0001

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR009 NET 24 S

FIR010 NET 24 S

FIR015 NET 24 S

FIR003 NET 24

FIR015 NET 24 S

FIR110 PEC 5 P

FIR111 PEC 5 P 6

FIR104 PEC 5 P

FIR004 NET 24

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

XMI000 24 : RSIG link lost - Reinitialized

FIR003 NET 24

FIR015 NET 24 S

FIR110 PEC 5 P

FIR104 PEC 5 P

FIR004 NET 24

XMI000 24 : RSIG link lost - Reinitialized

FIR009 NET 24 S

FIR010 NET 24 S

FIR015 NET 24 S

FIR011 NET 24 S 6

FIR104 PEC 5 P

FIR115 PEC 5 P

XMI000 24 : Msg from FPEC error #0001

XMI000 24 : Msg from FPEC error #0001

XMI000 24 : Msg from FPEC error #0001

TIM454 15:45 23/5/2005 CPU 1

AUD000
 
Looks like loop 24 is having some troubles. Also check FIJI cards and fibre that connects them.
 
i would agree with a fiber problem, if you've got a maint contract, call asap, if not test everything having to do with loop 24

john poole
bellsouth business
columbia,sc
 
I got a hold of our maint contract people. They remoted in and said it appears the Network card on Loop 24 reset itself because of a interupption in the fiber and there guessing the interupption was because of a static discharge possibly from something. We checked around the IT department and nobody was messing with any cabling anywhere at the time. So who knows what happened. I been watching for any more errors and nothing else has popped out. Oh well hopefully it stays working :)

We did have our fiber lines tested about a month ago and there all good according to those tests.

Thanks
 
yellow alarms are not in your switch, thats why they are yellow.. static does not come in on fiber.. that was excuse 23, on the list of vendor blowing smoke resons.. yellow could be no closer then the demark in the switchroom.

john poole
bellsouth business
columbia,sc
 
I think our Maint Support people are lousy. I know enough to do my daily routines and a little more advanced stuff but I have told these people how to do things before.

Then when they remoted in just today I told them to check the other loops while they were at it and they discovered Loop 8 and 10 were dead. They even admitted that they should of had an alarm tell them that. Those Loops arent used except as a back up to AT&T if they go down. So we wouldnt of had a backup to fall to right away. She said all she had to do was bring them back up. But still we paid them $32,000 for i think it was a 3 year contract. Part of that is 24/7 Monitoring.

We bought a new bulding and by next year were getting a whole new PBX so I cant wait for that and then we'll get a different Maint Contract too.
 
a vendor makes all the diff. once a day go to load 60 and type stat, that will check all of those t1 pri loops at once. lcnt will show all errors, if any number is not 0, call the vendor and have them FIX not just reset the loop.. btw, next time that contract is open, i only charge 23 grand to notmonitor of fix stuff

john poole
bellsouth business
columbia,sc
 
there is not a switch on the market that you can depend on without routine maint, because of basic service, i would never recogmend any switch to anyone large enough to buy a redundant switch anything except a 81c.. btw i also work on 11 switches besides nortel. two of which i am better at then the grey beast..

john poole
bellsouth business
columbia,sc
 
I'VE GOT A WHOLE LOT OF SWAMPLAND DOWN HERE IN FLORIDA, LOOKING FOR A BUYER

OLD ROLMEN WORKING ON NORTELS
 
LOL

I do go into ld 60 daily and do lcnt and see almost all of my loops with slips and LOSFA

Heck I just did a rcnt about 2 hours ago and look at what it says already...

TTY #15 LOGGED IN ADMIN2 19:32 23/5/2005



>ld 60

DTI000

.lcnt



DTI TRK LOOP 8

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -000

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 9

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -000

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 10

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -001

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 11

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -001

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 18

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -000

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 19

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -001

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 44

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -001

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 45

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -001

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 46

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -001

OS_BPV -000

OS_LOSFA-000

OS_YEL -000





DTI TRK LOOP 47

TRSH CNT:

BPV -000

SLIPD -000

SLIPR -000

CRC -000

LOSFA -000

OS_BPV -000

OS_LOSFA-000

OS_YEL -000



I have actually sat and reset it every hour and watched the slips and losfa's come back.

They tell me thats normal and nothing is wrong.

Most of the time there -001 and -002 but I have seen them rarley get up to -042 I think was the highest.

 
If 24 acts up again I would disable it until you could get it checked, when you flood the PBX with that many error messages it will INI again on you.
 
have your vendor fix the problem, slips are not normal or allowed, i have 40 plus t's and do not accept a single slip as normal. the lcnt table is not there to ignore. when you pay for maint, you only get what you demand. people blame nortel for switches going down when 99 out of 100 times it is poor or no maint.. with almost 7000 stations in this switch, i have 1000 sets up at all times. that is 500 open app's, i don't need 1000's of errors to handle at the same time, ram fills up cpu's begain to see backplane delay, causes more errors, data storm, ini.. some tech thinks it's because he used the mov command..

john poole
bellsouth business
columbia,sc
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top