Troubleshoot potential DSP hardware problems
Print View
by: Chris McAndrew
Total views: 10
Word Count: 1918
Although defective DSP's are not a common occurrence, the following document describes the symptoms and corrective action to be taken in the unlikely event a defective DSP card is installed on the 3300 ICP.
A variety of symptoms may be encountered when a faulty DSP card is installed in the 3300 ICP. The table below identifies the symptoms and corrective action to be taken.
|
Failure Type
|
Symptoms
|
Remedy Steps
|
|
|
|
|
|
Card Fails to come out of Reset
|
Both PostSoftware and PostMaintenance logs are generated as well as a "DSP Card Status" alarm.
|
The controller needs to be unplugged and plugged back in to get around the problem. Newer versions of DSP’s have been updated to prevent this issue from occurring.
|
|
|
|
|
|
Dsp Fails to Boot
|
No DSP resources. No dialtone on analog devices, embedded voicemail ports don't function, etc.
|
Remove and reseat the card. Reboot. They should be looking at the connectors for bent pins etc. NOTE: Ensure that the screws are not over tightened! Over tightening of one side can cause the other side connector to rise up.
|
|
|
PostSoftwareLog: StartUp (BindId=0) pCOam->coDspBoot failed with: DSP_PROGRAM_ERROR for card: 3 and dsp: 0
|
If the problem persists, then remove/replace the card completely. This card only needs to be immediately replaced if it is the only card/dsps being used for Telephony. If it was being used for Telephony, but there are still dsps left in the system, this is still fine but the user may be traffic limited until it is replaced.
|
|
Dsp Run-Time Access Fault
|
These are mostly exceptions that either produce an XRTC file or simply perform a hard reset on the system. These can occur at any point after the card has been taken out of reset but are considered separate from the Booting
Process. |
If the system is stuck in a reboot sequence. Remove and reseat the card. Reboot. They should be looking at the connectors for bent pins etc. NOTE: Ensure that the screws are not over tightened! Over tightening of one side can cause the other side connector to rise up.
Obtain System Diagnostics Reporting output, or at a minimum, the XRTC and PostSoftwareLogs. |
|
Dsp Overflow Error
|
As of R7.0, these are now tracked and monitored by the DSP Service Provider. If these occur, the dsp will be taken out of service and a "DSP Status" alarm is raised.
|
If this happens, and it is a HW problem, it should be repeatable. Remove and reseat the card. Reboot. Look at the connectors for bent pins etc. NOTE: Ensure that the screws are not over tightened! Over tightening of one side can cause the other side connector to rise up.
|
|
|
Prior to R7.0, these were only reported as PostSoftwareLog: RsrcAlloc() failed with result DSP_OVERFLOW.
|
If it is a pre R7.0 system: From the RTC shell, enter: DumpCaps (x,y) where x is the card number and y is the dsp number reported in the PostSoftwareLog. Capture these results and send them to Mitel Product Support.
|
|
|
|
Obtain System Diagnostics Reporting output file and contact Mitel Product Support.
|
|
|
