Cato Networks Knowledge Base

How to Reset an X1500B Socket (USB Drive)

This article explains how to reset an X1500B Socket to the factory image using an USB drive.

Cato has two certified Socket hardware models for x1500 sites (x1500 and x1500B). Make sure that you identify the exact Socket model before installing the image on the Socket.

For more information about the two X1500 Socket models, see Overview of Reimaging Cato Sockets.

Identifying the X1500B Socket Model

In May 2022, Cato introduced a second hardware model for the x1500 Socket. The new hardware model is referred as X1500B and it uses a different image than the X1500 Socket.

There are two ways to identify the X1500B model, the PSU (power supply unit) port on the back panel, and the sticker on the underside of the Socket.

  • PSU on the back panel

    X1500B_Back_Panel.png
  • Sticker on the underside

    X1500B_Sticker.png

If you install the X1500 image on an X1500B Socket, you can cause the Socket to stop working.

Resetting the Socket to the Factory Default Configuration and Version

Resetting the Socket to the Factory Default Configuration and Version

  1. Download the X1500B mage file IMAGE_INSTALL_socket_X1500B_BR2_12332_production_socket_v13.0_20211205_2022_04_11.dd.tgz

  2. Untar the image.

  3. Get a USB drive with at least 8GB of storage space available.

Burning the X1500B Image to the USB Drive

This section explains how to burn the Socket image to the USB drive for Windows, macOS, and Linux.

After you untar the image, compute the file hash of the uncompressed DD image file and then compare it to the Cato verified, correct file hash. This confirms the disk image integrity before writing the Socket firmware to the hard drive.

  • You can download a file with the verified hash here

  • Save the file to the same directory as the uncompressed disk image

Burning the Image with Windows

  1. Connect the USB drive to your Windows device.

  2. Untar the image, from the elevated Powershell in the same directory as both files, run tar -xf <archive-filename>

    Note

    Note: Common decompression software (such as Winzip, 7zip or Winrar) will corrupt the image, resulting in a file that is ~135MB in size. Extracting the file using the Windows CLI tar command should result in a file size that is larger than 1GB.

  3. Run the following command to compare the file hash of the Socket image:

    (Get-FileHash -Algorithm SHA256 
    .\IMAGE_INSTALL_socket_X1500B_BR2_12332_production_socket_v13.0_20211205_2022_04_11.dd).Hash -eq 
    (gc .\IMAGE_INSTALL_socket_X1500B_BR2_12332_production_socket_v13.0_20211205_2022_04_11.dd.sha256.txt).split()[0]

    The command returns True when the hashes are the same.

  4. Download and install disk imager software, such as Win32 Disk Imager.

  5. Write the image to the USB drive. (You may need to show all the files with *.* to see the DD file)

Burning the Image with macOS

  1. Connect the USB drive.

  2. Open a terminal window.

  3. Identify the new drive using the command diskutil list

  4. Unmount the identified drive using diskutil unmountDisk diskN

  5. Untar the image.

  6. Run the following command to compare the file hash of the Socket image:

    shasum -a 256 <archive-filename>
    Compare the output of this command with the verified hash above.
  7. Run this command dd if=./<file name> of=/dev/diskN bs=16m (WARNING: MAKE SURE YOU WRITE THE IMAGE ON THE USB DRIVE AND NOT ON YOUR HARD DISK)

    For example dd if=./IMAGE_INSTALL_socket_X1500B_BR2_12332_production_socket_v13.0_20211205_2022_04_11.dd.tgz of=/dev/diskN bs=16m

Burning the Image with Linux

  1. Connect the USB drive to your Linux machine

  2. Identify which device is your USB /dev/sdb or /dev/sdc

  3. Untar the image.

  4. Run this command dd if=./<file name> of=/dev/sdX (WARNING: MAKE SURE YOU WRITE THE IMAGE ON USB AND NOT ON YOUR HARD-DISK)

    For example dd if=./IMAGE_INSTALL_socket_X1500B_BR2_12332_production_socket_v13.0_20211205_2022_04_11.dd of=/dev/sdX

Installing the Image on the Socket

Was this article helpful?

2 out of 2 found this helpful

Comments

1 comment

  • Comment author
    Yaakov Simon

    Updated article for v13.0 Socket image

    0

Please sign in to leave a comment.