[Ascend] (ASCEND) Fine then, here is some traffic:

[Chris Clements]

Take a look at this fatal-history report.

WARNING:  Index: 179  Load: tbaxkh.m60 Revision: 7.0.3
        Date: 05/01/2001.       Time: 23:29:57
        Location: b02837b4 b0285aec b02ea528 b013979c b01923c0 00000000

WARNING:  Index: 179  Load: tbaxkh.m60 Revision: 7.0.3
        Date: 05/01/2001.       Time: 23:29:57
        Location: b02837b4 b0285aec b02ea528 b013979c b01923c0 00000000

SYSTEM IS UP:  Index: 100  Load: tbaxkh.m60 Revision: 7.0.3
        Date: 05/01/2001.       Time: 23:32:58

WARNING:  Index: 195  Load: tbaxkh.m60 Revision: 7.0.3
        Date: 05/03/2001.       Time: 11:47:32
        Location: b0213094 b027c51c b027ced4 b027db38 b027b758 b01923c0

FATAL ERROR:  Index: 1  Load: tbaxkh.m60 Revision: 7.0.3
        Date: 05/03/2001.       Time: 11:47:57
        Location: b0210a48 b0212fe0 b027c51c b027ced4 b027db38 b027b758

SYSTEM IS UP:  Index: 100  Load: tbaxkh.m60 Revision: 7.0.3
        Date: 05/03/2001.       Time: 11:51:08

This max periodically reboots itself as seen above.  The Index 179 error
seems to indicate that this is a problem related to ISDN calls.  In the
event that a fatal error occurs right after this warning the message is
intended to provide debug information.  Do you guys think that these reboots
are software related?  This max is running 7.0.3.


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request at bungi.com
Archives: http://www.nexial.com/mailinglists/