MICS keeps going down 1

[cpds]

This is our 2nd MICS at this location; it has XC7.1 SW, PRI, DTI, 6 port combo, 6 port expansion with 14 ASM's. This unit will freeze up sometimes once a week. Time and date will be on the phones but no intercom dial tone and none of the buttons will work. Here are the EVT and ALM codes we are getting. The provider says they see no errors on their end on the circuit. ANY help on this issue would be greatly appreciated. We are at a loss.
SYS TEST LOG
10/25/22
11:30 SYS STARTUP
11:30 EVT 299
11:30 EVT 462-01610101
11:32 EVT 367-0001 S5
11:33 ALM 372-0
11:34 ALM 50-09 3
11:36 EVT 680-1 S9
12:10 EVT 310-3C0005E5
12:10 EVT 799-000301S7
14:11 EVT 904-0108003C
14:13 EVT 310-36000200
15:16 EVT 310-3C0005E5
10/26/22
09:50 EVT 310-63000200
10:22 EVT 310-3C0005E5
10:22 EVT 310-36005A00
12:09 EVT 310-3C0005E5
12:10 EVT 799-000301S7
12:10 EVT 799-000401S7
12:10 EVT 310-3C0005E5
12:11 EVT 799-000401S7
14:20 EVT 904-0108003C
14:21 EVT 799-001703S7
10/27/2022
04:20 EVT 462-01610101
04:22 EVT 367-0001 S5
04:25 ALM 50-09
04:27 EVT 680-01 S9
04:27 UTAM CODE REQ'D
05:34 EVT 299
05:34 EVT 462-01610101
05:36 EVT 367-0001 S5
05:37 ALM 372-0
05:38 ALM 50-09
05:40 EVT 680-01 S9
05:40 UTAM CODE REQ'D

NETWORK EVT LOG
10/25/2022
11:33 EVT 372-0
10/27/2022
05:37 EVT 372-0 6 TIMES
Thanks for your help.....

 

[curlycord]

More to try if still an issue, my old workmate aragon (smarter than I) mentioned to try one or both:
CSU OFF
Change NI2 to DMS100

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN

 

[cpds]

Thanks curlycord, System went down again last night. I will try your suggestions as soon as I can get to site.

 

[cpds]

Still having trouble with system going down. I did find ASM bad that was causing the 247 codes. System down all lights on the DTI card or flashing. Rebooted turn the CSU off and within 20 minutes system went down. Rebooted now I have the green light and the amber light on the DTI card showing the circuit is down, I turned CSU back on. Call spectrum they are asking me do I want them to supply clocking or do I want them to supply the clocking. I thought they always supplied the clocking correct?

 

[libellis]

Normally the Carrier supplies clocking. Before changing that or anything else, I would do one simple thing. Put a much longer cable (100' or even 150') between the MICS and the carrier gateway to add some attenuation on the off chance the amplitude settings are causing over drive on the equipment with only the short (6') cable. (This is easier, faster, and less disruptive than changing drive level settings on both boxes.) If that doesn't work then I'm out of suggestions, but you could still try some of Curlycord's suggestions including replacing the 6-port expansion with a 6-port combo card or trying the DMS100 protocol (or confirming with the carrier that its gateway is really set to NI-2). At least the cause of the 247 event is now known so the focus is back on the link.

 

[cpds]

Libellis & curlycord thanks a lot for your input this is the only place I can get information on Nortel. I have two combo cards in the system, I tried turning the CSU off but when I do the system goes down within 10 minutes. I confirmed with spectrum's engineer that the PRI settings are NI2, ESF, ISDN, B8ZS. I've changed out the t1 cable added 125 ft will monitor. Thanks again for your input...

 

[cpds]

I have a question when I turned the CSU off and the system went down as it's been (time and date, buttons don't work, and no intercom dial tone) would that make you think it's the circuit? If just making a change to the PRI settings would that cause the system to lock up?

 

[libellis]

Early on I did say that I didn't understand how the carrier circuit could cause such a problem. I still don't, but that was what led me to thinking of the possibility of clocking problems due to a high line level/short cable issue, even though it would be unusual if that is indeed the problem (although not unheard of in other contexts). Even now I'd be quite surprised if it fixed the problem (for your sake I really hope it does). I did wonder if somehow enough corrupted D channel data could gum up the MICS, but I really don't know. By the way, presumably the MICS is programmed to access the PRI B channels for outbound calls in the opposite order to that of the carrier inbound, although I truly don't see how getting that wrong could create such a system problem.

 

[curlycord]

This is the FAQ I pointed out to you but not all is answered.

The bolded is your settings (answered)

----------
Example:
DMS-100 NI12
BCHANSEQ: DESEND OR ASSEND= use to opposite of TELCO
COFAIL:TIA-547A
I/F LEVELS:ISDN
FRAMING: ESF OR SF
INTERNAL CSU: ON OR OFF: LEAVE ON
CSU LINE BUILD:0
LINE CODING: B8ZS OR AMI: NORMALLY SET TO B8ZS
CLOCKSRC: PRIMARY OR SECONDARY
----------

CSU Line Build - Gain level of the transmitted signal
Options are 0, 7.5 or 15 dB.
0 is the default

Trying DMS 100

Does CSU stats show anything related?
Maybe do loop back testing with the carrier.

Is the KSU in with the hydro, transformer on the floor? and was replaced recently?

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN

 

[curlycord]

Just to be sure since it kind of points to the NVRAM...

NVRAM, are you sure it's Release 2?
I just caught Amazon selling s R2 when the image shows as R1
Then I see other sites also doing the same.

The variations of both should show as:

NTBB08GA-93 01 (or Rel 01)

NTBB08GB-93 02 (or Rel 02)

This is cheap!

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN

 

[cpds]

Here's what I have here in the shop it's the same NTBB08GA-93 02, are you saying that is a rel 01?

 

[curlycord]

This is what my master Nortel list states:
22. Norstar MICS NVRAM R1 [NTBB08GA-93]
23. Norstar MICS NVRAM R2 [NTBB08GB-93]

So this time I googled B instead of A and found this one which is confusing because the image shows that the box it came in is B but the Cartridge is A.

B appears to be a "kit" , but kit's usually contains more than 1 item.

I guess my list is part wrong because I found this thread.

exsmogger is probably right in his explanation.
Nortel should have change the part # to begin with.

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN

 

[cpds]

Curlycord thanks for the information your input is greatly appreciated. I remember back in 2003 or 2004 we did two systems in one week. One worked great the other one we could call in but not out. After hours of testing we found out the NVRAM was a rel 01 not 02. If the system goes down again I think I'll try your suggestion and change to DMS100. I have two other systems programmed the same way same provider within a 5 mile radius. Test logs show a lot of 310 codes but they don't go down, go figure.....

 

[cpds]

Received this in an email today from Spectrum engineer

As far as the settings for the clocking.

basic configuration:
framing: T1_FRAMING_ESF_CRC6
line-code: B8ZS
clock-master: CLOCK_MASTER_ON (We are providing clocking)

 

[libellis]

With the most recent changes have you logged into the system to see if it's still getting a lot of events even though it hasn't crashed?

 

[cpds]

Libellis, yes I login every day.

1/23 Last time system went down and I added the long T1 cable

1/24 & 1/25 Test log had one EXT 310

1/26 Test log showed system startup logs but time on system was correct and site said they didn't reboot

1/27 Test log showed EVT 312 The clock server received an unexpected event or invalid
FUMP message received by the clock.
1/27 Test log showed EVT 313 The clock server did not receive the clock alarm from the
N15 after a time-out period.

 

[libellis]

Don't you just love such helpful information like "invalid FUMP message". I guess time will tell if it's going to crash since it still gets clock related events (and why the startup events). When Spectrum tested the link did they do a complete loopback right to the handoff port (maybe used a loopback connector)? If not, they really should have.
Were the 6-port combo card and the long cable installed at the same time, or did you have the combo card in and the system crashed and then added the cable?

 

[cpds]

The comb cards were in when the system went down. I added the cable after that. Spectrum is coming out today or Monday to do some testing on the circuit.

 

[libellis]

I hope their testing includes loopback right to the hand off. At this point, with all you've done, the suspicion falls back on them. The other sites shouldn't really be seeing all those 310 events either.

 

[cpds]

I login to one of the other sites that is not going down and the test log had 50 all 310's. Do you know what EVT 904 is, I can't find anything on that EVT.

 

[curlycord]

I post 904 on the 3rd post from the top.

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN