Cisco AS5300 Access Server platforms experience a VTSP-3-DSP_TIMEOUT error


Wed, 11/18/2009 - 18:28
Jun 18th, 2009
User Badges:
  • Gold, 750 points or more

Core Issue

During the operation of a Cisco AS5300 Access Server, the user receives this message on the console or in the syslog:

%VTSP-3-DSP_TIMEOUT: DSP timeout on event 6: DSP ID=0x2312: DSP error stats


DSP_TIMEOUT messages indicate that the chassis CPU lost contact with a Digital Signal Processor (DSP) channel, and it reset the DSP in order to clear the problem. Generally, this    reset is sufficient to resolve the problem, and no further action should be    taken. If there are repeated messages that affect the same DSP IDs or similar    DSP IDs, perform these steps:

  1. Make sure you have the correct version of VCware and DSPware that matches      the Cisco IOS  Software version on the AS5300 Access Server. A mismatch on      the Cisco IOS Software and VCware could cause the problem, so it must be ruled out first. You can verify this information by issuing the      show      vfc [slot number] version vcware and show      version commands.
  2. Reset the DSPs on the VFC, and check to see if the status is back      to active and that there are no DSPs "asleep" on the board.
  3. After you reset the DSPs on the VFC board, or reset the entire VFC board, make sure that the status of the DSPs is correct. You can issue the test dsp command, and then issue the show pool command to show  you the status of all the DSPs. The DSPs should all be in the Free queue.
  4. After you have reset, monitor the values of the DSP IDs over time for the AS5300 Access Server which exhibit the problem.
  5. Analyze the DSP_TIMEOUT messages. If they re-appear nearly instantly, reseat the VFC by a power-down of the AS5300 Access Server.

    Note: The AS5300 Access Server modules are not hot-swappable, and it is highly recommended  that you shut down the router and restart it promptly, or go through a warm reboot through the Command-Line Interface (CLI).

  6. If the problem continues, identify patterns in the DSP IDs found. For example, you may observe that all DSP IDs start with the same digits. Typically the first two or three digits do not change over time. If the DSP IDs follow such a pattern, you may experience a hardware failure. To verify if this is a hardware failure, swap the VFCs from slot one to slot two, and confirm that the DSP_TIMEOUT messages reference the new location of the hardware. Determine whether the problem follows the new VFC slot number or if it stays the same.
  7. There may be more than one DSP module failure on a VFC. It is best to compile a list of DSP IDs that appear in the messages and sort it by ascending order to easily identify patterns.
  8. If the DSP_TIMEOUT messages re-appear once you reset the VFC and reload  the access server, you are likely to experience a software problem. You      should escalate the case for proper debugging.

For detailed information, refer to Troubleshooting    VTSP-3-DSP_TIMEOUT Error on Cisco AS5300 Access Server Platforms.

Problem Type

Gateway or module

Failure Type

Drops out, times out, flaps, toggles, hangs, gets stuck, locks up, loops, temporary pause, stops responding, cuts short, etc.

Error message

DSP Errors

%VTSP-3-DSP_TIMEOUT: DSP timeout on event [dec]: DSP ID=[hex]: [chars]

Digital Signal Processor (DSP) Related


Voice Gateways

AS5300 Series Universal Access Server



This Document

Related Content