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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Has anyone solved the 'Warm Start Reason 36' yet??

Status
Not open for further replies.

ct56

MIS
Jul 22, 2003
2
US
I have been fighting this problem for several months now. I found the related thread on this site, but I don't see any indication that anyone has found an answer to the problem. I have had 3 (yes 3) different vendors look at the problem and I have spoken to Nortel ETAS about it. Not one single person has had a definitive answer for me. Some have told me to upgrade to 25.40, but it appears to me that people are having this problem on different versions of the software. Others have told me to change out the SSC, but this particular SSC ran for over 2 months on load 24.24r_16 without any INI'ing at all. It wasn't until I loaded 24.24r_18 that the INI'ing reared it's ugly head. Are we all chasing 'slightly' different problems??? I would feel much better if I could find someone who has actually solved this problem. I thought for sure that someone in ETAS would have run across the problem by now.

Please help:}

Confused in Houston.....
 
In my opinion, you need to nail down nortel, for this prob. as they made the darn box. and if you have registered this switch, and have all your ducks lined up correctly, nt is obligated to help. post the code agin.
 
I agree with you completly. The switch is registered properly. The big problem with Nortel is that we as owners are forced to either work through a Channel Partner or lay out some HUGE bucks to be part of the COAMS program. Since we don't have a lot of money, we have continued to attempt to resolve the problem via Nortel Partners.

Below is the exact same information that I have sent to Nortel ETAS. When I dig into the output codes, I end up at a point in the manuals that says 'Contact your support representative'.

Thanks for your response.

******************************************
Hi XXXXX,

Here is the information on our switch and the problem that I have been experiencing. Please have one of your techs call me as soon as they can so we can set up a time to take an indepth look at this problem. (Monday morning if at all possible.)

Our switch is an Option 11c with one extension cabinet using a fiber channel link.
software: x11 24.24_R18.
SSC: NTDK20AB RLS 18 (2 fiber ports)

Currently, in cabinet 1 we have:

4 T1's interfaced via TMDI 1.5m DTI/PRI NTRB21AA Rls 10 cards. 2 are local loops (SBC) and 2 are ld loops (Broadwing)
5 NT8D02GA Rls 07 Digital line cards
1 NT8D09BA rls 05 Analog Line Cards W/WLC

Cabinet 2 has:

4 NT8D09BA ANalog Line cards w/WLC (in slots 7-10)


The problem we are experiencing is detailed in the text attachment to this email. We have been experiencing this since I upgraded the switch to 24.24_r18. At first I thought it was a problem with that generic of software, but I have since contacted other people who are having the identical problem on 24.40 and 24.10 versions.

The switch will be running great with a load or with no load and then just do a warm boot. The INI003 message is always the same. My analysis of the messages following the reboot leads me to believe that we are loosing communications with our expansion cabinet OR possible only with the analog cards in it.

When the switch does its warm boot, we almost always loose communications with our analog cards, BUT that could be because we are running automated dialers on those circuits and they continue requesting service while the switch is rebooting. At any rate, the problem is DEFINITLY NOT load related as it will happen at 3 or 4 a.m. when there is no traffic at all on the switch.

Well, that's pretty much all I can think to relay to you guys that you can't get out of a data dump on the switch.

******************************************


TIM000 02:00 22/7/2003 CPU 0

DTC103

DTC103

AUD000

DTC103
Warm Start begun - reason 36
interrupt: Error changing SL1 priority


*** OS RESTART ***


Meridian 1 X11 System Software
Release : x112424
Created : Thu Jun 10 22:46:53 PDT 1999
Loaded : 22/7/03 2:32:56
Last Restart: 21/7/03 14:15:09
Current Time: 21/7/03 14:15:09

Copyright(C) 1972-1997 Northern Telecom, Inc. All Rights Reserved.
VxWorks 5.2
Copyright(C) 1984-1995 Wind River Systems, Inc. All Rights Reserved.

Initialize Network Interface.

Network Interface is up.

Host : PRIMARY_ENET

IP Address : 137.135.128.253

Sub-netmask : 255.255.254.0


Executing startup script "c:/p/etc/startupc".
# EDITION AH02, SL1LIB TRINH.439 (99/04/17 15:50:22) -- CLOSED
# Empty startup file for use in the field.
cd "c:/p/etc"
value = 0 = 0x0

Done executing startup script "c:/p/etc/startupc".
0x202fa0c4 (tRptD): (22/7/03 2:32:44.000) SRPT0789 RST 0: Exception-caused task restart: TID=0x20458260, vec=0x2, pc=0x2002bf0e

0x202fa0c4 (tRptD): (22/7/03 2:32:44.000) SRPT0786 RST 0: Task tSL1 being restarted

PDT: Unable to preserve macro library contents.
0x202fa0c4 (tRptD): (22/7/03 2:32:45.000) SRPT0782 RST 0: WARM START IN PROGRESS - Reason 36

[ Initialising Orbix Error handling ]
[ Constructing a new Proxy Factory Table ]
Loading MAT script files......
Start SNMP agent
Processed c:/p/data/view.cfg

INI000 00000000 02 33 43 00000000 00000000 00000000 00000000 ? 00000000
DSET000 DOWN LOAD 0 0 0 0 0 0 0 88740517

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


INI003 000000EF
ACDR ACTIVATED

AUD000

SRPT731 OS 0: Warm Start
Release: x112424
Created: Thu Jun 10 22:46:53 PDT 1999
Last Cold Start: 21/7/03 14:15:09 (from 'flash ROM')
Last

SRPT754 INI due to System Restart
Previous INI: 21/ 7/03 14:16:33
INIs since cold start (21/ 7/03 14:16:33): 2

SRPT752 INI 0: INI completed in 21 seconds

DTC103

DTC103

TIM000 03:00 22/7/2003 CPU 0

AUD000

DTC103

DTC103

AUD000

DTC103

DTC103

AUD000

TIM000 04:00 22/7/2003 CPU 0

 
I recently had this same problem with a refurb Opt 11 c. It turned out to be the soft ware daughter board.

 

I'm inclined to agree with 1brc, change the software daughterbooard, then move toward the SSC card(ssc prob ok)
it looks like its a read write prob. to mem. or from mem.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top