Acme Packet: How to Use Dump Commands to Obtain More Detailed Troubleshooting Information

Asset ID:	1-71-1597874.1
Update Date:	2017-05-10
Keywords:

Solution Type Technical Instruction Sure

Solution 1597874.1 : Acme Packet: How to Use Dump Commands to Obtain More Detailed Troubleshooting Information

Applies to:

Acme Packet 4500 - Version S-Cx6.3.0 and later
Acme Packet 3820 - Version S-Cx6.3.0 and later
Acme Packet Legacy Platform Hardware - Version All Versions and later
Information in this document applies to any platform.

Goal

How to use 'dump' commands to obtain more detailed troubleshooting information.

Solution

The following "dump" commands can be used on 3000 and 4000-series hardware, to dump detailed information to the /code directory, and later provided to Acme Packet Technical Support for analysis:

dump-tasks

Function: Creates file /code/taskCheckDump.dat
Content: Displays stack data for suspended tasks

Note: The dump-tasks command is not supported on SCZ7.X

dump-statistics

Function: Creates file /code/stats.dump
Content: Displays all SIP,MBCD,H323,MGCP statistics and "show process all"

dump-nvram

Function: Creates file /code/log.nvram
Content: Displays historic record of errors written to console

dump-np-stats

Function: Creates file /code/npstats.dump, or /opt/logs/dump.datapath on SCZ7.x release
Content: Displays Network Processor statistics

For 4500-series systems equipped with ETC (enhanced traffic control) network cards:

dump-etc-all

Function: Creates the file /code/dump-etc-all.xz
Content: contains statistics and debug information in the event of a problem with the ETC card (crash, or hang, etc)

Fortunately, since these commands are written to /code instead of /ramdrv, the files they generate are stored persistently, even across system reboots. Some files also rotate after a certain size to keep them from taking up too much space in the /code or /opt/logs partition.

Attachments

This solution has no attachment