FIR 103 PEC 11 continuous error with SL-1 Assertion failed thrown in as a bonus

[rickrock09]

Nortel CS1000 in a Hospital environment throwing errors and im not sure where to start troubleshooting. It streams FIR 103 PEC 11 then FIR 104 PEC 11 S. Also about every other line shows ASRT001 SL-1 Assertion Failed. In the last few minutes it has added DTC001 and ERR9050 21 0 to the mix. Can someone provide me with some knowledge please?

 

[KCFLHRC]

From the Avaya Solutions Page


avaya-logo
Subscribe Subscribe Printer Friendly Version Printable version Email Email
CS1000: FIR103 & FIR104
Rate Content Rate this Page

Doc ID: SOLN189860
Version: 6.0
Status: Published
Published date: 15 Jul 2010
Updated: 13 Apr 2017
Author:
Content Migrator

Details

5554723
Problem Clarification
Products affected
Communication Server 1000
CS1K
NT1P61CA
NT1P62EA

Scenario
FIR103 & FIR104
FIR103 & PEC 4
FIR104 & PEC & 4 & P
Cause

.
Solution

1) Disable FPEC
2) Re-seat FPEC at remote.
3) Disable FNET card
4) Re-seat the FNET card.
Legacy ID
KB95554723

 

[KCFLHRC]

So basically you have an issue with your fiber remote

 

[rickrock09]

established a new fiber path from cs 1000 to the remote cabinet, disconnected the fibers on the remote to swap and expected to see a light come on. didnt get a light or error or anything on the switch. feel like it is the daughterboard on the remote cabinet
att rep said the errors were basically saying that it was running on secondary, runs a test on primary to verify it is ok and the test fails. so it appears to me the card in the remote cabinet just needs replacing to start with

 

[rickrock09]

finally got a maintenance window to troubleshoot this further. Disabled the loop, backed the card out and installed new card with 2 new daughter boards on the fiber remote. established a new pair of fiber from card to card including jumpers. one of the jumpers on the remote side was part of the issue but regardless stopped the FIR errors and lights out....everybody happy....BUT now a steady stream of ASRT001 SL-1 Assertion Failed streaming down the page. An occasional DTC 001 error pops in, not sure if they are related but thought I should mention.

Anyone have ideas to resolve ASRT001 SL1 assertion failed

 

[KCFLHRC]

Only 1 solution on this from Avaya, see below


Subscribe Subscribe Printer Friendly Version Printable version Email Email
CS1000 7.5 sw: ASRT0001 SL-1 Assertion Failed is not documented in NTP
Rate Content Rate this Page

Doc ID: SOLN205605
Version: 4.0
Status: Published
Published date: 06 Jul 2012
Updated: 02 Dec 2014
Author:
Mario Larsen

Details

TTY printed a message that is not documented. Need to know what this message refers to.

ASRT001 sl-1 assertion failed.
CS1000
Rls 7.5
Problem Clarification

TTY printed out messages "ASRT0001 SL-1 Assertion Failed" while PRI loops were coming up after upgrading Call Server to release 7.50Q.
Message description in 7.6 NTP NN43001-712_06_Ac_System_Messages_Alarms_Reference_CS1000_7.6.pdf


Cause

ASRT0001 SL-1 Assertion Failed messages were occurring because of excessive input messages being received on channel 24 of loops 11 and 78. Both of these channels are configured on this switch as D Channels, but both D Channels showed as being in RLS status.

pdt> rdgo 570
[0570] 07/11/2013 11:06:51 ASRT0001 SL-1 Assertion Failed
pdt> rds 4
[0570] 07/11/2013 11:06:51 ASRT0001 SL-1 Assertion Failed
edi = 02383000 esi = 02700001 ebp = 02cbc5b0 esp = 02cbc580
ebx = 02cbc588 edx = 00000053 ecx = 00000000 eax = 00000000
eflags = 00000216 pc = 01a19be4

Return Address Stack:
011bb2e8 (SL1ASSERT+18)
01d391df (OVERLOAD$CARD_OVERLOAD$SEND_ONE_MSG+2f)
01d38fb4 (OVERLOAD$CARD_OVERLOAD$SEND_DISABLE_MSG+23c)
01d3852d (OVERLOAD$CARD_OVERLOAD+455)
01d38047 (OVERLOAD+37)
01cf6fbb (WORKSHED$OVL_TIMING_256MS+c7)
01ce76bc (WORKSHED$T_128MSEC_MARK+ec)
01ce694a (WORKSHED$INPUT_TASK+1ea)
01cdf8f6 (WORKSHED+132)
132bafaa (NW_APPEND_DGTS$APP_0_TO_NDN+11272)
0222cdec (vxTaskEntry+c)
Stack (top = 0x2cbc580):
02cbc580: 00000001 02cbc64c 02383000 02700001 02cbc5b0 02cbc580 02cbc588 00000053
02cbc5a0: 00000000 00000000 00000216 01a19be4 02cbc5c0 011bb2e8 02700001 011bb2b8
02cbc5c0: 02cbc5d8 01d391df 00000000 02383000 02cbc64c 00000001 02cbc5f8 01d38fb4
02cbc5e0: 02cbc64c 02cbc668 00005324 02383000 02cbc64c 00000001 02cbc648
01d3852d called SEND_DISABLE_MSG
02cbc600: 02cbc64c
02cbc668
00005324 SAVE_TN (being passed on to send_disable_msg)-------------------------------
00000000 0000000f 00000000 00000000 00005324 <<Local SAVE_TN variable
02cbc620: 00000000 00000000 00000000 00000001 0000000a 00000000 00000000 02383000
02cbc640: 02cbc668 00000000 02cbc664 01d38047 02cbc668 00000000 02383000 02cbc6d4
02cbc660: 00000000 02cbc680 01cf6fbb 00000000 00000000 02383000 02cbc6d4 00000000
02cbc680: 02cbc69c 01ce76bc 02cbc6d4 00000000 02383000 02cbc6d4 00000000 02cbc6b8
02cbc6a0: 01ce694a 02cbc6d4 00000000 02383000 02cbc6d4 00000000 02cbc6d0 01cdf8f6
02cbc6c0: 02cbc6d4 00000000 00000000 00000000 02cbc6e0 132bafaa 00000000 00000000
02cbc6e0: 00000000 0222cdec 00000000 00000000 00000000 00000000 00000000 00000000
02cbc700: 00000000 00000000 00000000 00000000 00000000 00000064 0000002f 0519b638


conv 5324
=> 083 0 09 00 SCH2038

SCH2038
Channel to TN conversion failure.
Solution

ASRT0001

SL1 Assertion Failed. An assertion made in the core telephony software has failed. A condition that is expected by software to always be true is not.

Action: report the problem to the operating company, including the stack trace from the report log.


Disable and reseat PRI loop associated in the RAS data

 

[rickrock09]

turned out a recent INI left a loop Enabled that had nothing connected to it. Disabled the loop and errors stopped. Thanks for your help