I believe that in this case you should contact the TAC. FE1's are 'Fatal Assert', but the warnings typically give a good indication of the cause. Either that or you can download and read the latest release notes from www.esight.com or ftp.ascend.com, and see if there are any reported Generally Available (GA) fixes for the type of problem you are seeing now. Greg > -----Original Message----- > From: Stephen Hovey [mailto:shovey at buffnet.net] > Sent: Sunday, April 01, 2001 1:51 AM > To: ascend-users at bungi.com > Subject: (ASCEND) fatal index:1 and 195 errors > > > > What is a fatal index:1 mean? I have a 6000 that keeps > rebooting itself. > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to > ascend-users-request at bungi.com > To get FAQ'd: <http://www.nealis.net/ascend/faq> > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>