How can I generate a debug dump on Blue Coat Director?

<< Back to Knowledge Search



How do I create a debug dump on Blue Coat Director?

How do I upload the Director debug dump to Blue Coat for analysis?


Complete the following tasks to generate and send the debug dump file on Blue Coat Director

Task 1 - Generate a debug dump file

To generate a debug dump file: 

  1. Log in to the CLI and enter enable mode.
  2. Check the local logging level (the default is notice): 
     #show logging
  3. Set the local logging level to debug:
    #config t 
    logging local debug
  4. Reproduce the issue that you are troubleshooting.
  5. Generate the debug dump file:
    (config)#debug dump generate
    You will see the dump file successfully generated as example output below:

    Generating debugging dump... 
    Dump file successfully written to ciqinfo-Director-20xx.xx.xx-xxx.tgz
  6. Set the local logging back to its previous setting:
    (config)#logging local <level>
    For example, if the previous setting was notice, enter #(config)logging local notice.

Note: For steps on creating archives or retrieving an overlap file, refer to 000008073.

Task 2: Upload the debug dump file

To upload the debug dump file, use Method 1 below. Use Method 2 only if Method 1 fails.

Method 1: (Preferred method) Upload the dump file to a local FTP server 

  1. In the CLI, view the debug dump logs:
    (config)#show debug dumps
  2. Take note of the name of the dump file you created in Task 1.
  3. Upload the dump file to an FTP server:
    (config)#debug dump upload <name of dump file> ftp://<FTP_Server>/<name of dump file> username <username> password <password>
    where <FTP_Server> is the IP address or DNS name of the FTP server.

Method 2: (Use only if Method 1 fails) Upload the dump file manually via shell command

Note: Do not use this method unless Method 1 fails. 

  1. In the CLI, go into shell and upload the dump file manually. Enter the following CLI commands:
    (config)# shell
    Releasing the configuration lock.
    # cd /local/userfiles
    # ls
    cIQconfig_050202     dump?ciqinfo-Director-20xx.xx.xx-xxx.tgz
    # mv dump?ciqinfo-Director-20xx.xx.xx-xxx.tgz Debug_dump.tgz
    # ftp
    ftp> open
    220 ftp server name banner appears here
    ftp> bin
    220 Type set to I.
    ftp> put Debug_dump.tgz
    local: Debug_dump.tgz remote: Debug_dump.tgz
    227 Entering Passive Mode ()
    150 Opening BINARY mode data connection for Debug_dump.tgz.
    100% |*************************************| 11173 KB    1.10 MB/s
    00:00 ETA
    226 Transfer complete.
    11441308 bytes sent in 00:09 (1.09 MB/s)

Task 3  -  Upload the dump file to Support File Uploading Form

Upload the dump file to the Support File Uploading Form at

Include all pertinent information in the form, including the Service Request Number (support ticket number).


Additional Information
Bug Number
InQuira Doc IdKB4183

Article Feedback

Hide Properties
First Published      10/01/2014
Last Modified      10/01/2014
Last Published      10/01/2014
Article Audience
Product      Director
Topic      Debugging
Article Number      000009904
Was this helpful?
Previous MonthNext Month