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

DSI Excep - system rebooting

Status
Not open for further replies.

rtctechlv

IS-IT--Management
Oct 24, 2005
3
US
We recently upgraded our system to 5.22 and the system reboots randomly. I corrected several issues in the config after the upgrade and I am now receiving the following error after a cold reboot. All physical connections, including power have been checked and everything is fine so it is not a power issue.
Reason: Abnormal Termination
Termination Cause: <DSI Excep> addr=7002d884 d=5 pc=f01d11a8 stack=f01d115cf01d1314f00bde70f00b8094f01d1b94
I have not been able to find any information on the DSI Excep error.
 
that is something only Avaya will be able to tell you... you can try upgrading to the latest 5.0(24)
 
We are running 5.0.18 and had this happen today. The carrier was onsite and swears they did not do anything to the PRI T1 but I'm suspicious..I looked at the log dump from syslog and found :

671789mS PRN: ALARM: 12/07/2010 12:58:42 IP 500 5.0(18) <DSI Excep> CRIT RAISED addr=00002304 d=5 pc=f01dd250 f01dd370 f0317fe8 f03183b8 f03184a4 f0371380
671789mS PRN: ALARM: 26/07/2010 09:02:19 IP 500 5.0(18) <DSI Excep> CRIT RAISED addr=00003104 d=5 pc=f01dd250 f01dd370 f0317fe8 f03183b8 f03184a4 f0371380
671789mS PRN: ALARM: 28/10/2010 13:02:36 IP 500 5.0(18) <DSI Excep> CRIT RAISED addr=00002304 d=5 pc=f01dd250 f01dd370 f0317fe8 f03183b8 f03184a4 f0371380
671789mS PRN: ALARM: 13/01/2011 10:51:58 IP 500 5.0(18) <DSI Excep> CRIT RAISED addr=00002304 d=5 pc=f01dd250 f01dd370 f0317fe8 f03183b8 f03184a4 f0371380
 
Upgrade it to 5.0.24 and see if it comes back.


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
The upgrade worked! I believe in the docs for the new version, it states a fix for the system reboot that is linked to the VM Pro which we also were running. It was a while ago and I dont remmemeber the specifics. Bottom line, it worked!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top