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!

FATAL DSI Exception

Status
Not open for further replies.

saulz

Technical User
Feb 28, 2005
33
I Keep getting this in my ip412 3.2.55 and keeps on rebooting. Was wondering if anyone knows what could be causing it? Thanks

45588986mS RES: Wed 16/5/2007 09:37:37 FreeMem=10613064(58) CMMsg=21 (22) Buff=200 838 999 1390 2 Links=5195 Elements=124
45589386mS PRN: Begin Stack Trace
45589387mS PRN: pc=00944ba8
45589387mS PRN: lr=0094e088
45589387mS PRN: 00000000
45589387mS PRN: 0094e088
45589388mS PRN: 0097f5a8
45589388mS PRN: 0097245c
45589388mS PRN: 00972a9c
45589388mS PRN: 008e5c14
45589389mS PRN: 008e5e08
45589389mS PRN: 008e5eac
45589389mS PRN: 008e2560
45589389mS PRN: 008e2534
45589390mS PRN: End Stack Trace
45589390mS PRN: .FATAL DSI Exception address=04100000 d=10 pc=00944ba8 00000000 0094e088 0097f5a8 0097245c 00972a9c 008e5c14 008e5e08 008e5eac 008e2560 008e2534 00000000 00000000 00000000 00000000 00000000 00000000 IP 412 3.2(55)

********** contact lost with 10.1.1.10 at 09:42:56 16/5/2007 - reselect = 4 **********


Alarm dump shows this.

3001mS PRN: +++ START OF ALARM LOG DUMP +++
3001mS PRN: ALARM: 04/05/2007 11:41:37 IP 412 3.2(55) <TLB Instruction Error> CRIT RAISED addr=aaaaaaa8 d=12 pc=aaaaaaa8 008e3834 00944838 00976eb0 009a5014 0097f57c
3001mS PRN: ALARM: 04/05/2007 11:45:25 IP 412 3.2(55) <DSI Exception> CRIT RAISED addr=20000044 d=4 pc=00a5da48 01b4ccd8 00a5e8b0 008e2560 008e2534 00000000
3001mS PRN: ALARM: 08/05/2007 08:52:52 IP 412 3.2(55) <DSI Exception> CRIT RAISED addr=0af7e92e d=16 pc=008e4980 009e3a40 008e4c08 008ef364 00ce3a70 00ce2054
3002mS PRN: ALARM: 08/05/2007 08:55:18 IP 412 3.2(55) <DSI Exception> CRIT RAISED addr=20000044 d=4 pc=00a5da48 01b57a70 00a5e8b0 008e2560 008e2534 00000000
3002mS PRN: ALARM: 11/05/2007 18:39:48 IP 412 3.2(55) <DSI Exception> CRIT RAISED addr=20000044 d=4 pc=00a5da48 01af83f8 00a5e864 008e2560 008e2534 00000000
3002mS PRN: ALARM: 16/05/2007 09:37:38 IP 412 3.2(55) <DSI Exception> CRIT RAISED addr=04100000 d=10 pc=00944ba8 00000000 0094e088 0097f5a8 0097245c 00972a9c
3002mS PRN: +++ END OF ALARM LOG DUMP +++
 
defaultthe unit and built up your config from scratch
probably your config is corrupt
it is hard to geus what is going on but give it a try


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
What is a DSI Exception?
 
if i knew then i would be rich
nobody knows
i think even avaya does not know
something went wrong
thats all it tells


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
A DSI exception occurs when a data memory access cannot be performed.

Report to Avaya with the full trace wich shows the fault, the will investigate and can provide a private build wich solves the problem.
 
These errors are very generic, ie Avaya may be able to tell you it is related to digital extensions for example, but that would be all.
You need the full trace - information for several minutes before the reboot, and ideally two or more traces to tell exactly what is going on.

 
What is Avaya Direct Tech support number that im sopposed to call?
 
If you don't have direct contact with Avaya you are probably supposed to take this issue through you Business Parter or Distributor.
 
Saulz, did you ever get to the bottom of your rebooting IP 412? If you did what was the resolution?

Saulz said:
Keep getting this in my ip412 3.2.55 and keeps on rebooting. Was wondering if anyone knows what could be causing it? Thanks

45588986mS RES: Wed 16/5/2007 09:37:37 FreeMem=10613064(58) CMMsg=21 (22) Buff=200 838 999 1390 2 Links=5195 Elements=124
45589386mS PRN: Begin Stack Trace
45589387mS PRN: pc=00944ba8
45589387mS PRN: lr=0094e088
45589387mS PRN: 00000000
45589387mS PRN: 0094e088
45589388mS PRN: 0097f5a8
45589388mS PRN: 0097245c
45589388mS PRN: 00972a9c
45589388mS PRN: 008e5c14
45589389mS PRN: 008e5e08
45589389mS PRN: 008e5eac
45589389mS PRN: 008e2560
45589389mS PRN: 008e2534
45589390mS PRN: End Stack Trace
45589390mS PRN: .FATAL DSI Exception address=04100000 d=10 pc=00944ba8 00000000 0094e088 0097f5a8 0097245c 00972a9c 008e5c14 008e5e08 008e5eac 008e2560 008e2534 00000000 00000000 00000000 00000000 00000000 00000000 IP 412 3.2(55)
 
IPmonkey, I just went back to 3.1.65 and everything is working good. The 3.2.55 did not like my 412 with my config. I will soon try to update to 3.2.57 and see what happens.
 
saulz said:
IPmonkey, I just went back to 3.1.65 and everything is working good. The 3.2.55 did not like my 412 with my config. I will soon try to update to 3.2.57 and see what happens.
saulz, let me know how you go on with your upgrade to v3.2.57. We have a site on v3.2.54 with the same problem.
Is the IP 412 part of a SCN, or is it stand alone?
 
Its part of a SCN we have 6 other sites. Actually some 5 are now on 3.2.57 and 1 other on 3.1.65. So far everyhting is ok. This weekend i will try to upgrade the 3.165's.
 
it is not a version problem
if you see the alarms you already had alarm before the upgrade
export your config and default the unit
then upgrade it and import your config
before you import check your config with the 3.2 manager to see if there are any faults in it


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Those alarms are only from 3.2.55. We were on that version since April. I also did a fresh config with same results. My other branches experienced the same issues while on 3.2.55. Now they are on 3.2.57 with no complaints and no random reboots.
 
strange that a 3.2.55 gives problems and a 3.2.57 not
but everything is possible with software :)
then you know what to do now


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
saulz said:
Its part of a SCN we have 6 other sites. Actually some 5 are now on 3.2.57 and 1 other on 3.1.65. So far everyhting is ok. This weekend i will try to upgrade the 3.165's.
How's the SCN setup? is it programmed as a star or mesh network, Star ie. 1 central site (vm pro centralised) with all other systems pointing to that site or has it got IP routes direct (mesh) to the other systems?
Im just trying to get to the bottom of a rebooting 412 that is part of a SCN but is set up currently as a mesh network and has vm pro's also at the other sites, its the only system on the SCN network that is rebooting with TLB errors!

tlpeter said:
strange that a 3.2.55 gives problems, and a 3.2.57 not
but everything is possible with software
tlpeter, is that not why maintenance releases are brought out? to fix software problems!!!!!!!!!!
 
ipmoney
mesh network is not supported also like multiple vmpro's in a scn


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
tlpeter you sound like an Avaya robot, I know its not allowed now, but when a system's been set up and working fine in a mesh network for 2 years on 2.1 with an index media gateway backbone with the aim of giving the customer as much flexibility and functionality as they had with there reliable Index systems then some configurations need to be tailored to what the customer wants and the stock answer of "its not supported" is sometimes not quite good enough. In the early IP O days the star network was not defined as the correct way to network systems.
Remote queuing is was also not supported on centralized voicemail.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top