fun it is. Even though it's 1:30 AM, I'm going to drive 2 hours to move the card to a different slot to see if the DSPs will come back up. If not, I'll be ordering a replacement. I'm just glad it's Thursday, as I'll have a light load tonight and can get a replacement card on Friday. I needed to order a couple new cards anyways, I just didn't expect to be an emergency type thing. *sigh* -- Troy Settle Pulaski Networks 540.994.4254 - 866.477.5638 http://www.psknet.com > -----Original Message----- > From: owner-ascend-users at max.bungi.com > [mailto:owner-ascend-users at max.bungi.com] On Behalf Of Faisal > Sent: Wednesday, October 23, 2002 8:40 AM > To: ascend-users at bungi.com > Subject: (ASCEND) Maxtnt Fatal-error Index 179 > > > Hi, > > We see a lot of these messages : > > WARNING: Index: 179 Revision: 9.0.9 Slot 1/5 (tntmadd) > Date: 10/18/2002. Time: 13:03:49 > Location: e01e9900 e01e9c28 e01e9e6c e01d0160 > e01d7d14 e0053e70 > > > WARNING: Index: 179 Revision: 9.0.9 Slot 1/5 (tntmadd) > Date: 10/18/2002. Time: 13:03:49 > Location: e01e9900 e01e9c28 e01e9e6c e01d0160 > e01d7d14 e0053e70 > > > WARNING: Index: 179 Revision: 9.0.9 Slot 1/5 (tntmadd) > Date: 10/18/2002. Time: 13:04:46 > Location: e01e9900 e01e9c28 e01e9e6c e01d1818 > e01d7ca8 e0053e70 > > > Now this Index: 179 means ' Unexpected Error ' , how to find > out what actually went wrong ? should we configure a core > dump server and get the dump when this happens ? if yes, then > how to analyse that dump ? Is there any analyser/debuger etc > ? or is it that we have to send it to Lucent Support/tech ?? > > Or, can any one tell me someother way to find out what > actually went wrong with these cards ? > > Thanx & Regards, > > Faisal > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to > ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/