FAQ

How do I run the hardware diagnostics on the SG9000, SG900, SG600, SG300, CF5000 and CF500 appliances?

FAQ ID:    FAQ1337
Version:    17.0
Status:    Published
Published date:    03/29/2013
Updated:    10/18/2013
 

Answer

Confirm availability of the Customer Diagnostics on the appliance

  • Beginning with SGOS 5.4.3.7, a CLI command exists to show if any customer diagnostics code is present and the version of the diagnostic code
  • Customer Diagnostics are available on SG9000's manufactured on or after the Aug 16 2010.

NOTE: The manufacturing date of a ProxySG can be seen based on its serial number.
The first 4 numbers represent the week number and year that a given device was manufactured.

For August 16 2010, this corresponds to a serial number of 3310xxxxxx where 3310 = the 33rd week of the year 2010.
A newer example would be a serial number for March 5 2012, which corresponds to 1012xxxxxx, where 1012 = the 10th week of the year 2012.

To check if the Customer Diagnostics are present on the appliance

  1. From the CLI, enter:

ProxySG> en
ProxySG# show diagnostic-systems

If the output from this command indicates that a version of Customer Diagnostics code is present, proceed to the next section for steps to access the diagnostics.

  1. If no diagnostics code is present on the system, enter the following CLI commands from CLI config mode.
    NOTE: if uploading/upgrading to Diagnostics 2.1.4, you must be running or upgrade to 6.2.7.1 or later or run 6.3.x.x. or be running 5.4.3.7 or higher in the 5.x branch.

ProxySG# (config)diag-upgrade-path https://...
ProxySG# (config)exit
ProxySG# load diag-upgrade

The URLs to access the Customer Diagnostics code are platform specific.  Use:

Platform

HW Diag Version

Link

SG300

2.1.4

https://bto.bluecoat.com/download/direct/diag/sg300-diag.bcsi

SG600

2.1.5

https://bto.bluecoat.com/download/direct/diag/sg600-diag.bcsi

SG900

2.1.4

https://bto.bluecoat.com/download/direct/diag/sg900-diag.bcsi

SG9000

2.1.4

https://bto.bluecoat.com/download/direct/diag/sg9000-diag.bcsi

CF5000 MX

2.1.4

https://bto.bluecoat.com/download/direct/diag/cf5000-mx_diag.bcsi

CF-500 KX

2.1.4

https://bto.bluecoat.com/download/direct/diag/cf500-kx_diag.bcsi


Accessing Customer Diagnostics on this platform (using the serial console cable)

  1. During bootup, when you see seconds remaining display onscreen, press the space bar to interrupt the default boot image selection to select an alternate system image.

  2. Enter d when a list of available Customer Diagnostic versions appear.

  3. Enter s if you wish to go back to the normal boot image menu.

  4. Select the menu number of the version of Customer Diagnostics you wish to load.

  5. After the Customer Diagnostics are loaded and running, the Diag> prompt will appear.

Note: The following process will interrupt 'Production' traffic, as the unit needs to be restarted.

Using the Customer Diags on this platform

  1. Enter log on to record the output to memory.

  2. Type ? or Help to see the list of available commands. Help <command> gives a description of the command.

  3. Run tests using the following commands (Depending on the diagnostics version commands may differ): 

    The following command changes the diagnostics level for the memory and disks. Default is Level 1. Level 2 runs more indepth tests and takes longer to complete.
  • level <1 | 2>

            The following commands should be run for a complete diagnostics test.

  • test mem

  • test disk

  • test env or show env

  • test ssl

  • test hwscan or show hardware

  • test all (This tests memory, disks and SSL components)

    The following commands require physical access to the front-panel on appliance:
  • test lcd
  • test keypad or test fpd 

Note: Pressing CTRL-C will stop a test 

  1. If running a newer diagnostics version you can upload the logs to an existing SR. First you have to configure an IP, Gateway and DNS. NOTE: This does not change the configuration of the appliance.

  • show network
  • config ip 1:0 <ip address> <netmask>
  • config gateway <ip address>
  • config dns <ip address>
  • log upload SR#

     5.    Otherwise upload the log manually.

  • After performing tests, start "logging" from within the terminal application (e.g. Hyperterminal, PuTTy, etc).
  • Enter log display to print the recorded log output.
  • The Customer Diagnostics will begin displaying all test data/output, beginning with the first test that was run.
  • Stop "logging" from within the terminal application.
  • Restart the appliance to exit Customer Diagnostics. You can also enter exit in the CLI prompt.

 

 


Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question