PacketShaper ceases passing traffic and the management interface stops responding


Article ID: 185074


Updated On:


PacketShaper S-Series


The PacketShaper has ceased passing traffic and stopped responding on the management interface.

The console port displays a login prompt, but once logged in as a touch or look user, there is no way to log out. If this condition is suspected, only log in to the console as a recovery user.

If the appliance is in a hung state, and if you are logged into the console port as a look or touch user, the console port also becomes unusable, which renders data gathering impossible.


PacketShaper S-Series appliances, running any 11.x version.


Hang issues related to host list configuration have been resolved in PacketShaper 11.5. This version also includes additional diagnostic functionality via the recovery menu.

Upgrade to upgrade to 11.5 or later to resolve this issue.

Version contains a fix for bug 227627, the bug for which this article was initially written.

PacketShaper S-series core file generation

Follow the process below if your PacketShaper is in a hung state and cannot be accessed via a web browser or remote login utility, or if you have been asked to provide a core file for any other reason.

CAUTION: Do not log in to the console port as a touch or look user; you must log in as a recovery user as described below.

  1. Access the PacketShaper via the console port.
  2. Enter the username recovery with the password recovery.
  3. Select option 6. Soft restart.
  4. Enter yes when asked if you want to proceed.
    You will see a "Please Wait" message for about 5-10 seconds.
  5. When the recovery menu reappears, type "0" to exit.
    For approximately 60-80 seconds, the PacketShaper may be inaccessible, after which point the management functionality should become available and the PacketShaper should respond to pings.
  6. When the PacketShaper is available, log in via a web browser and click on the Advanced UI link at the top right of the page.
  7. Go to the Info tab, and click the File Browser button.
  8. Browse to 9.256/log.
    This folder contains core files, back traces, and the associated log files. A single crash will generate four files (with a fifth essentially being to replace latest.log with the most recent backtrace). These files can be grouped together either by the dates of their creation, or by the PID at the time of the crash, typically a 4-5 character long numeric value immediately before the file extension.
  9. Locate the five most recently created files, or find one, and copy the PID, and find each instance of it in this directory. Check the box next to each of those files, and at the top of the page click the zip radio button. Enter a file name that's 8 characters or less; omit the .zip.
  10. Click Go. When the Results of file operations area show that it has added each of the selected files, the archive is complete.
  11. Click Update to see the zip file listed in the directory. Click the zip file to download it.
  12. Upload the zip file to against the support case open for that device. Alternatively it can be uploaded directly to the service portal at by logging in and selecting the support case to which the issue applies.

If you cannot gather this data for any reason, but the shaper is unresponsive as described, reboot the device, and escalate the case.