BUG Errors...

[JustShady]

Hello all,

Would someone please tell me what "BUG4005 Lost time slot idle Call Register"
actually means?

I have had 2 system INIs in the past 2 weeks (yesterday was one) where the system basically restarts itself downing the entire system for about 10 minutes.

This BUG error is the only one that contantly shows although I did get the following after the crash.

AUD017 00000008 0000FEDE 0000FFDE

AUD019 00008220 00001F80 00004004

AUD017 0000003F 0000FEFE 0000FFFE

TFS501 63 1 0

AUD000

Looking at the history this morning, everything looks clean. Any clues?

Thanks in advance,

JustShady

 

[johnpoole]

those bugs are not causing ini's.. couple of things i would do.. ld 117 inv generate midnight.. then the next day and any day after that.. ld 117 inv print sets.. do a compare between as built and actual.. mismatches and phones that are missing waste bandwidth and cpu time.. a few other things that can cause ini problems.. phones that have the same scr. if you have depts set up with all the phones the same

key 0 scr 1000
key 1 scr 1001
key 2 scr 1002
key 3 scr 1003


when the number of ringing phones excedes the amount of cpu or bandwidth on the backplane, or call registers,, ini. another problem i've seen is lhk set past the last scr key or lhk's that cover just the mcr key... hunts to sets that are gone... if your software is clean, less chance of an ini. before i got to this site, ini every two weeks or so.. in the last two years.. none.. we do use the mov command and we do use the cpy command..

here's another problem i have found in the past.. ld 30 out of drol.. a disabled set takes less bandwidth then a working set.. an enabled set that is unplugged takes over twice the bandwidth as a working set...

when i was a boss i used to tell my inhouse techs, clean up your software or clean out your desk... nortel is not a switch that we can see how much we can get by with.. once it gets bad enough to ini, then it can be a little late to clean house... the next problem you will see is usually, corruption tn/dn problems.. the tn or dn will show vacant but try to use it and the sch tells you it's being accessed..

john poole
bellsouth business
columbia,sc

 

[NTOldTimer]

If you can copy and paste the INI code here that will give clues to those that may help you here.

 

[a12ozbottle]

You wont see anything in the history file after an ini, except what occurs after it. Post the ini codes.

 

[JustShady]

This might be more than what you need... thanks for taking a look.

JustShady

SYS000 000400 000000 000000 000000 CPU 0
SYSDB RLS/ISS: 2540B LOADED FROM C: DATE/TIME: 9/12/2006 04:01:26 RECS: 103 SEQNO: 391
SYSLOAD ISSUE 25.40B
INI000 00000000 17 14 33 00000000 00000000 00000000 00000000 00000000
SRPT752 INI 0: INI completed in 14 seconds

DSET000 DOWN LOAD 1914 0 186 2 0 0 0 142218

INI002 00000088 00000086 00000087

INI003 000000B0 000000B4 000000B8 000000BC 000000CE 000000D0 000000D4 000000D8 000000EE


INI003 000000EF

INI006 00000082

ELAN019 ELAN Server enabled after M1 INIT

XMI002 XFIL 1

XMI002 3 EXUT

XMI002 4 XDLC

XMI002 6 XDLC

XMI002 8 XMLC

XMI002 9 MGATE

XMI002 10 MGATE

XMI007 10

XMI002 12 XDLC

XMI002 14 XDLC

XMI002 16 XDLC

XMI002 18 XDLC

XMI002 1 TMDI

XMI002 5 XDLC

XMI002 15 XDLC
XMI002 17 XDLC
XMI002 19 XDLC
XMI002 7 XDLC

XMI002 13 XDLC

XMI002 11 EXUT
SCR002 0

DTC105 0

TMDI300 1 FROM: SYS DSBL - SELFTESTS PASSED TO: ENBL
TIME: 17:15:12

DTA003 1

PRI000 1 5

DTC007 0

DTA005 1

DTA007 1

DCH2040 11 3

DCH: 11 EST CONFIRM TIME: 17:15:28 12/12/2006

TRK156 3 0 0 0

TRK156 3 0 0 2

DTA015 1

TRK156 11 0 0 1

 

[janeenaj]

The INI is normal after a power on reset SYS000 0400. Your system lost power

 

[janeenaj]

or someone toggled the power switch on the SSC card

 

[janeenaj]

@a12ozbottle

INI does not clear the history file, sysload will though

 

[a12ozbottle]

My mistake...thanks for the correction.
Is this an ac or dc switch or option 11?

 

[JustShady]

This is an AC switch connected to a large UPS. So I surmise that it is either a faulty UPS or faulty power supply on the switch... Thanks guys!

 

[acewarlock]

You had a System Reload not an INI, an INI last about a min or so tops.

 

[JustShady]

John, you had me thinking... what am I doing wrong here?

Each phone's DN is a dedicated DID. In the case of 3903s and up, there is a rollover DN (eg; 6424/5424). If an extension is not being used... it's outed. If someone leaves a phone unplugged... the port is automatically disabled. When I set up a new phone on a new port... I usually cpy from another DN and chg what needs to be changed. If I move a phone... I move the wire. The only problems I rarely encounter are unplugged phones and someone occasionally leaving the page port open. I have had the PRI go down a couple of times(CO) and, after these sytem reloads a couple of phones have been locked up and and ports have needed to be disu and enlu.

I do not see much about maintenance routines in this forum and not being properly trained, I probably need to spend more time at least checking system errors and other system information. Any recommendations?

This forum, a couple of others and as much documentation as I have been able to muster has been my only saving grace. I have learned alot here and I appreciate the time you all take to respond to these enquiries. I'm sure others do as well.

Thank you so much,

JustShady

 

[janeenaj]

one of the first thing you migh want to do is move your CallPilot from slot 9 and 10 to 8 and 9. Nortel put out a bulletin not to long ago stating that the CallPilot is not supported in slot 9 and 10.

from the power up, i don't see you have anything in slot 2, you could move your analog that's currently in 8 to 2 to make moving the CP over to 8 and 9.