CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Packet Voice Digital Signal Processor Modules (PVDMs) provide the hardware digital signal processing (DSP) power required by Cisco routers to terminate analog and digital time-division multiplexing (TDM) voice circuits, perform codec transcoding, host hardware conference bridges, and anchor Media Termination Points (MTPs). Whether you are auditing hardware before a Unified Communications migration, sizing Cisco Unified Border Element (CUBE) transcoding capacity, or diagnosing call setup failures, verifying both the physical PVDM state and real-time DSP channel utilization is a core administrative task.

Checking a PVDM involves verifying physical hardware recognition at the chassis level, inspecting logical DSP core health and credit allocation inside Cisco IOS or IOS-XE, and monitoring active media sessions.

Verifying Physical PVDM Installation via CLI

To confirm whether a PVDM is physically installed in a Cisco router, recognized by the chassis backplane, and reporting a valid part number (PID) and serial number, follow this sequential CLI verification process.

Step 1: Check Hardware PID, Version, and Serial Number with show inventory

The primary command across both classic Cisco IOS and modern Cisco IOS-XE platforms to verify physical PVDM presence is show inventory. This command reads the onboard EEPROM of every detected module and outputs its exact slot location, product identifier (PID), hardware revision (VID), and factory serial number (SN).

Router# show inventory
NAME: "Chassis", DESCR: "Cisco ISR4331 Chassis"
PID: ISR4331/K9        , VID: V02, SN: FDO2012XXXX

NAME: "PVDM subslot 0/4", DESCR: "PVDM4-64 Voice DSP Module"
PID: PVDM4-64          , VID: V01, SN: FOC1945XXXX

NAME: "subslot 0/1 db module 0", DESCR: "PVDM4-32 Voice DSP Module"
PID: PVDM4-32          , VID: V02, SN: FOC1833XXXX

If your router has multiple interface cards, filter the output directly using show inventory | include PVDM or show inventory | section PVDM.

Step 2: Verify Subslot Operational State with show platform (IOS-XE)

On Cisco IOS-XE routers, physical detection in the inventory should be paired with show platform to confirm that the router’s chassis manager has initialized the PVDM subslot into an ok operational state:

Router# show platform
Chassis type: ISR4331/K9

Slot      Type                State                 Insert time (ago)
--------- ------------------- --------------------- -----------------
0         ISR4331/K9          ok                    42d05h
 0/0      ISR4331-3x1GE       ok                    42d05h
 0/1      NIM-2MFT-T1/E1      ok                    42d05h
 0/4      PVDM4-64            ok                    42d05h

Step 3: Inspect Detailed Board Diagnostics with show diag (Classic IOS)

On legacy Cisco IOS routers (such as the 2800, 3800, 2900, and 3900 series), show platform does not display subslot-level PVDM states. Instead, run show diag to view the motherboard PVDM SIMM sockets, EEPROM contents, and hardware assembly numbers:

Router# show diag | section PVDM
        Slot 0:
        PVDM2-64 SIMM (4 DSP) daughter card
          Hardware Revision        : 4.0
          Part Number              : 73-8539-04
          Board Revision           : B0
          Serial Number            : FOC1422XXXX

Step 4: Confirm Voice Subsystem Registration with show voice dsp summary

Once hardware detection is confirmed, run show voice dsp summary (or inspect the active configuration via show running-config | section voice-card) to ensure the IOS voice subsystem has bound a logical voice-card construct to the physical PVDM slot. Physical detection paired with an active voice-card entry proves the module is ready to allocate DSP channels.


Checking PVDMs Across Platforms: ISR G2 vs. ISR 4000 and Catalyst 8300

While show inventory works across all routers, the physical placement, naming conventions, and architectural rules for PVDMs differ significantly as you move from legacy ISR G2 routers to Cisco ISR 4000 and Catalyst 8300 Series Edge Platforms. Use this platform progression to interpret CLI slot outputs accurately.

1. Legacy ISR G1 and ISR G2 (2800, 3800, 2900, 3900 Series)

On ISR G1 and G2 routers, PVDM2 and PVDM3 modules are installed directly into dedicated PVDM slots on the router motherboard (Slot 0).
– Architecture Rule: Motherboard PVDMs on ISR G2 serve a unified pool. A single motherboard PVDM3 can simultaneously provide TDM voice termination (for T1/E1 VWICs) and IP media services (transcoding and conferencing).
– CLI Identification: Appears in show inventory under Slot 0 as PVDM2-xx or PVDM3-xx.

2. Cisco ISR 4000 Series (IOS-XE)

The ISR 4000 architecture splits PVDM4 deployment into two distinct physical locations—and understanding which slot you see in the CLI determines what services that PVDM can perform:
– Motherboard PVDM4 (PVDM subslot 0/4): All ISR 4000 models except the ISR 4221 and ISR 4461 include a single onboard motherboard PVDM4 slot, which always enumerates as subslot 0/4. A motherboard PVDM4 cannot be used for TDM voice termination; it is restricted exclusively to IP-based media services such as transcoding, conferencing, and media optimization.
– T1/E1 NIM-Mounted PVDM4 (subslot 0/x db module 0): To terminate TDM T1/E1 PRI or CAS circuits on an ISR 4000, a PVDM4 daughterboard must be physically mounted onto the Fourth-Generation T1/E1 Voice and WAN Network Interface Module (such as NIM-1MFT-T1/E1 or NIM-2MFT-T1/E1). In show inventory, this displays as subslot 0/<nim-slot> db module 0. Any unused DSP channels on the NIM-mounted PVDM4 can overflow to assist the motherboard with IP transcoding or conferencing once dsp services dspfarm is enabled under that voice-card.

3. Cisco Catalyst 8300 Series and ISR 4461 (NIM-PVDM and SM-X-PVDM)

The Catalyst 8300 Series and the high-end ISR 4461 do not have motherboard PVDM slots. Instead, they rely on dedicated slot-based DSP modules for IP media services (requiring Cisco IOS-XE 17.3 or later):
– Standalone NIM-PVDM (NIM-PVDM-32, -64, -128, -256): Installs directly into a standard NIM slot without needing a T1/E1 carrier card. It supports IP media services only (no TDM voice termination).
– High-Density SM-X-PVDM (SM-X-PVDM-500, -1000, -2000, -3000): Installs into a Service Module (SM-X) slot on Catalyst 8300 or ISR 4331/4351/4451/4461 platforms, scaling up to 3,080 low-complexity channels per module.
– CLI Identification: Run show platform to confirm the NIM or SM-X slot state, and check show inventory where the module enumerates directly under its NIM or SM subslot (for example, Subslot 0/2: NIM-PVDM-128). Note that analog modules (FXS/FXO) and BRI modules on ISR 4000 and Catalyst 8300 have built-in, non-configurable DSP chips and do not consume channels from installed PVDM4 or NIM-PVDM cards.


Checking PVDM DSP Utilization, Credits, and Active Channels

Confirming that a PVDM is installed only tells you theoretical capacity. Because modern PVDMs allocate resources dynamically using a credit-based “Flex DSP” architecture, you must inspect the voice DSP groups and DSP farm profiles to see how many channels and credits are actively consumed and how much headroom remains.

Step 1: Audit DSP Health and Credit Pools with show voice dsp group all

Run show voice dsp group all to inspect every DSP chip across all installed PVDMs. Each PVDM contains one or more individual DSP cores, and each core provides a fixed pool of credits (for example, 240 credits per DSP core on many PVDM3/PVDM4 modules).

Router# show voice dsp group all
DSP groups on slot 0/4:
dsp 1:
  State: UP, firmware: 4.4.706
  Max signal/voice channel: 16/16
  Max credits: 240
  Group: FLEX_GROUP_VOICE, complexity: FLEX
    Shared credits: 180, reserved credits: 0
    Signaling channels allocated: 2
    Voice channels allocated: 2
    Credits used: 30
  Group: FLEX_GROUP_XCODE, complexity: SECURE MEDIUM
    Shared credits: 0, reserved credits: 60
    Transcoding channels allocated: 1
    Credits used: 30

  0 DSP resource allocation failure

Evaluate the following key metrics in the output:
1. State: UP: Confirms the DSP core has booted and loaded its firmware.
2. Max credits vs. Shared credits / reserved credits: Max credits is the total capacity of that DSP chip. When you configure a dspfarm profile for transcoding or conferencing, IOS reserves credits (reserved credits) exclusively for that profile. Remaining credits stay in Shared credits for TDM voice termination.
3. Channels allocated and Credits used: Shows real-time utilization. Low-complexity calls (such as G.711) consume fewer credits per channel than medium- or high-complexity calls (such as G.729 or iLBC). To calculate free capacity on a DSP core, subtract Credits used (and any dedicated reserved credits locked by other groups) from Max credits.
4. DSP resource allocation failure: Located at the bottom of the output. Any number greater than 0 indicates that the router rejected a call or transcoding request because the PVDM ran out of DSP credits.

Step 2: View Per-Channel Call Activity with show voice dsp

To see exactly which voice ports or RTP streams are occupying individual DSP channels—along with the negotiated codec, packet counts, and signaling channel ID—run show voice dsp (or show voice dsp active to filter out idle channels):

Router# show voice dsp active
TYPE  DSP CH CODEC     VERS TS ABORT PACK-TX/RX      VOICE-PORT CHNL
===== === == ========= ==== == ===== =============== ========== ====
FLEX  001 01 g711ulaw  4.4  01     0    4510/4508    0/1/0:23   001
FLEX  001 02 g729r8    4.4  02     0    1204/1204    0/1/0:23   002

Step 3: Check Transcoding and Conferencing Profiles with show dspfarm all

When PVDMs are registered to Cisco Unified Communications Manager (CUCM via SCCP) or local CUBE (via LTI or SCCP) for transcoding, conferencing, or hardware MTP, inspect profile status and session usage with show dspfarm all and show dspfarm dsp all:

Router# show dspfarm all
Dspfarm Profile Configuration

 Profile ID = 1, Service = TRANSCODING, Resource ID = 1
 Profile Description :
 Profile Service Mode : Non Secure
 Profile Admin State : UP
 Profile Operation State : ACTIVE
 Application : CUBE   Status : ASSOCIATED
 Resource Provider : FLEX_DSPFARM   Status : UP
 Number of Resource Configured : 12
 Number of Resource Available : 10
 Codec Configuration: num_of_codecs:4
 Codec : g711ulaw, Maximum Packetization Period : 30
 Codec : g711alaw, Maximum Packetization Period : 30
 Codec : g729ar8, Maximum Packetization Period : 60
 Codec : g729abr8, Maximum Packetization Period : 60

Look closely at Number of Resource Configured versus Number of Resource Available to determine how many concurrent transcoding or conferencing sessions remain free in your allocated pool. Selecting the key operational metric here reveals whether your DSP bottleneck is physical hardware exhaustion (Max credits reached) or administrative profile sizing (maximum sessions set too low in the dspfarm profile).


Troubleshooting Undetected or Failed PVDM Modules

If a PVDM fails to appear in show inventory as covered above, or if show voice dsp group all reports unresponsive DSP cores, follow this diagnostic workflow to recover the module without causing unnecessary network downtime.

Step 1: Diagnose Abnormal DSP States (FAIL, DOWN, or APP_DOWNLOADING)

When checking show voice dsp group all, any state other than UP indicates a fault:
– FAIL or DOWN: A DSP core has crashed, experienced repeated DSP_TIMEOUT IPC errors, or suffered a hardware fault. Any voice call routed to a failed DSP core will immediately drop or fail to cut through audio.
– APP_DOWNLOADING or booting: The router is attempting to push DSP firmware to the module, or the module is stuck in a boot loop. If it remains in APP_DOWNLOADING for more than a few minutes, firmware transfer over the internal bus has hung.

Step 2: Perform a Soft CLI Reset of the PVDM or DSP Core

Before scheduling a physical power outage, attempt a software reload of the affected DSP or subslot:
– On Cisco ISR 4000 and Catalyst 8300 (IOS-XE): Reload the specific PVDM subslot using its slot/subslot coordinates:
text
Router# hw-module subslot 0/4 reload

– On Legacy ISR G1 and ISR G2 (Classic IOS): Reset the individual hung DSP chip without resetting the entire router:
text
Router# test dsp device 0 1 reset

(Where 0 is the slot number and 1 is the DSP ID shown in show voice dsp group all.)

Step 3: Isolate a Failed DSP Core During Production Hours

If a single DSP core on a multi-DSP PVDM fails during business hours and a soft reset does not bring it back to UP, the router may still attempt to allocate calls to that broken DSP, causing intermittent call failures. Take the defective subslot or DSP core out of service immediately so active calls only use healthy DSPs:
– On Cisco ISR 4000 and Catalyst 8300 (IOS-XE):
text
Router# hw-module subslot 0/4 stop

– On Legacy ISR G1 and ISR G2 (Classic IOS):
text
Router# test dsp device 0 1 remove

(Once replaced or recovered, test dsp device <slot> <dsp-id> restore returns it to the pool on classic IOS.)

Step 4: Verify Slot Compatibility, Licensing, and Physical Reseating Rules

If a newly installed PVDM does not appear in show inventory or show platform at all, check these four physical and software prerequisites:
1. Incompatible Slot Placement: Ensure a PVDM3 was not forced into an ISR 4000 (which requires PVDM4), and confirm you are not expecting a motherboard PVDM4 (subslot 0/4) to terminate TDM T1/E1 voice calls (TDM cards require the PVDM4 to be mounted directly on the T1/E1 NIM).
2. Minimum IOS-XE Version and UC License: Standalone NIM-PVDM modules require Cisco IOS-XE 17.3.1 or later. Additionally, voice DSP initialization requires the Unified Communications (uck9) technology package license to be active on the router (show license summary or show version).
3. Physical Reseating and Hot-Swap (OIR) Rules: Dust or uneven pin contact during shipping frequently causes missing PVDMs. While PVDM4 daughterboards mounted on T1/E1 NIMs support Online Insertion and Removal (OIR) when the NIM is gracefully stopped, motherboard PVDM4 modules are not hot-swappable. You must completely power down the router during a maintenance window before removing or reseating a motherboard PVDM.
4. Hardware RMA Validation: If reseating the card and upgrading firmware fail to clear a FAIL state—or if the PVDM works in a known-good chassis but stays stuck in booting on the target router—initiate a Cisco Return Material Authorization (RMA) for the defective PVDM or chassis backplane.


SNMP OIDs and Templates for Automated PVDM Monitoring

To continuously track DSP channel utilization and alert on failed DSP cores without manually running CLI commands, configure your Network Monitoring System (NMS) to poll CISCO-DSP-MGMT-MIB (Base OID: .1.3.6.1.4.1.9.9.86).

Cisco IOS / IOS-XE SNMP Configuration Template

! Enable SNMPv3 Read-Only access and DSP traps on the Cisco router
snmp-server view DSP-MONITOR iso included
snmp-server group NMS-GROUP v3 priv read DSP-MONITOR
snmp-server user NMS-POLLER NMS-GROUP v3 auth sha <AUTH_PASSWORD> priv aes 128 <PRIV_PASSWORD>
snmp-server enable traps dsp card-status
snmp-server enable traps dsp oper-state

CISCO-DSP-MGMT-MIB Key OID Reference Template

# Card-Level PVDM Metrics (cdspCardStatusTable)
# Indexed by entPhysicalIndex from ENTITY-MIB (.1.3.6.1.2.1.47.1.1.1.1.7)
cdspCardState                = .1.3.6.1.4.1.9.9.86.1.1.1.1.2   ; 1=normal, 2=warning, 3=critical, 4=fatal, 5=offLine
cdspCardResourceUtilization  = .1.3.6.1.4.1.9.9.86.1.1.1.1.3   ; Percentage (0..100%) of total card DSP channels in use
cdspTotalDsp                 = .1.3.6.1.4.1.9.9.86.1.1.1.1.7   ; Total DSP cores present on the card
cdspFailedDsp                = .1.3.6.1.4.1.9.9.86.1.1.1.1.8   ; Number of DSP cores currently in a failed state

# Per-DSP Core Channel Utilization Metrics (cdspStatusTable)
cdspOperState                = .1.3.6.1.4.1.9.9.86.1.2.1.1.1   ; 1=normal, 2=shutdown, 3=congested, 4=failed
cdspTotalChannels            = .1.3.6.1.4.1.9.9.86.1.2.1.1.6   ; Maximum channels supported by this DSP core
cdspInUseChannels            = .1.3.6.1.4.1.9.9.86.1.2.1.1.7   ; Channels currently reserved for call setup
cdspActiveChannels           = .1.3.6.1.4.1.9.9.86.1.2.1.1.8   ; Channels actively processing voice/media packets

Net-SNMP CLI Polling Script Template

#!/usr/bin/env bash
# Poll Cisco Router PVDM utilization and DSP channel counts via SNMPv3
ROUTER_IP="<ROUTER_IP>"
SNMP_USER="NMS-POLLER"
AUTH_PASS="<AUTH_PASSWORD>"
PRIV_PASS="<PRIV_PASSWORD>"

echo "=== PVDM Card Utilization (%) ==="
snmpwalk -v3 -l authPriv -u "$SNMP_USER" -a SHA -A "$AUTH_PASS" -x AES -X "$PRIV_PASS" \
  "$ROUTER_IP" .1.3.6.1.4.1.9.9.86.1.1.1.1.3

echo "=== Failed DSP Cores Count ==="
snmpwalk -v3 -l authPriv -u "$SNMP_USER" -a SHA -A "$AUTH_PASS" -x AES -X "$PRIV_PASS" \
  "$ROUTER_IP" .1.3.6.1.4.1.9.9.86.1.1.1.1.8

echo "=== Per-DSP Reserved Channels (cdspInUseChannels) ==="
snmpwalk -v3 -l authPriv -u "$SNMP_USER" -a SHA -A "$AUTH_PASS" -x AES -X "$PRIV_PASS" \
  "$ROUTER_IP" .1.3.6.1.4.1.9.9.86.1.2.1.1.7

echo "=== Per-DSP Active Voice Channels (cdspActiveChannels) ==="
snmpwalk -v3 -l authPriv -u "$SNMP_USER" -a SHA -A "$AUTH_PASS" -x AES -X "$PRIV_PASS" \
  "$ROUTER_IP" .1.3.6.1.4.1.9.9.86.1.2.1.1.8

Setting an NMS threshold alert whenever cdspFailedDsp (.1.3.6.1.4.1.9.9.86.1.1.1.1.8) exceeds 0 or cdspCardResourceUtilization (.1.3.6.1.4.1.9.9.86.1.1.1.1.3) exceeds 85% ensures proactive notification before call drops occur.


Cisco IOS Voice Command Reference and Documentation Guide

The following specifications provide the exact command syntax, privilege modes, argument definitions, and authoritative Cisco documentation locations for PVDM and voice DSP verification commands.

show voice dsp

  • Description: Displays the operational status, firmware version, credit allocation, or channel-level packet statistics for voice DSP modules.
  • Syntax: show voice dsp [group {all | slot <slot-number>} | active | summary | detail | crash-dump]
  • Command Mode: User EXEC (>) or Privileged EXEC (#).
  • Key Keyword Definitions:
  • group all: Displays credit pools, shared/reserved credits, and allocated channels for all DSP groups across all slots.
  • active: Filters output to show only DSP channels currently processing an active voice or media call.
  • summary: Displays a condensed table of DSP count and channel totals per voice-card.
  • crash-dump: Displays diagnostic memory register dumps for DSP cores that have transitioned to a FAIL state.

show dspfarm

  • Description: Displays configured DSP farm profiles, SCCP/LTI application associations, and DSP resource pool allocations for transcoding, conferencing, and hardware MTP services.
  • Syntax: show dspfarm [all | profile [<profile-id>] | dsp [all | active | stats]]
  • Command Mode: Privileged EXEC (#).
  • Key Keyword Definitions:
  • all: Outputs all DSP farm configuration parameters and current resource availability counters.
  • profile: Displays administrative state (UP/DOWN), operational state (ACTIVE/INACTIVE), associated application (CUBE or SCCP), and configured codecs for a specific profile.
  • dsp all: Lists individual DSP channels assigned to DSP farm pools and their current session states.
  • dsp stats: Displays packet-level transmit/receive statistics for active DSP farm sessions.

Official Cisco Documentation Navigation Paths

To access complete field-by-field descriptions and hardware installation rules on Cisco.com, consult these official manuals:
1. Command Syntax and Field Reference: Cisco IOS Voice Command Reference → Navigate to Chapter: S Commands → Locate show dspfarm and show voice dsp (show vdev through show voice statistics memory-usage).
2. Voice Card and DSP Farm Configuration: Cisco IOS Voice Command Reference → Navigate to Chapter: D through I Commands → Locate dsp services dspfarm and dspfarm (voice-card).
3. CUBE Transcoding and DSP Verification: Cisco Unified Border Element Configuration Guide (Cisco IOS XE) → Navigate to Media Manipulation and Profiles → DSP-Based Functionality Including Transcoding and Transrating.
4. Hardware Architecture and Channel Density Tables: Cisco Packet Voice Digital Signal Processor Modules (PVDM4, NIM-PVDM, and SM-X-PVDM) Data Sheet and Configure and Troubleshoot PVDM4 on Cisco ISR 4000 Series Routers (Cisco Support Document ID: 213250 / 118749).


Conclusion

Verifying a PVDM on a Cisco router requires checking both physical hardware state and logical DSP resource pools. Start by confirming physical detection and slot placement using show inventory and show platform, keeping in mind the architectural separation between motherboard PVDM4 slots, T1/E1 NIM daughterboards, and standalone NIM-PVDM or SM-X-PVDM modules on modern IOS-XE routers. From there, use show voice dsp group all and show dspfarm all to audit credit consumption and active media sessions, and integrate CISCO-DSP-MGMT-MIB into your monitoring platform so you always have visibility into your voice gateway capacity.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.