Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Verifying ISCSI Connections

 

Verify that the connections between a primary HA host or secondary HA host and an iSCSI device are operational.

  1. Using SSH, log in to the primary or secondary HA host as the root user.
  2. To test the connection to your iSCSI storage device, type the following command:

    ping iSCSI_Storage_IP_Address

  3. Verify the iSCSI service is running and that the iSCSI port is available by typing the following command:

    telnet iSCSI_Storage_IP_Address 3260

    Note

    The default pot is 3260.

  4. Verify that the connection to the iSCSI device is operational by typing the following command:

    iscsiadm -m node

    To verify that the iSCSI device is correctly configured, you must ensure that the output that is displayed for the primary HA host matches the output that is displayed for the secondary HA host.

    If the connection to your iSCSI volume is not operational, the following message is displayed:

    iscsiadm: No records found

  5. If the connection to your iSCSI volume is not operational, then review the following troubleshooting options:
    • Verify that the external iSCSI storage device is operational.

    • Access and review the /var/log/messages file for specific errors with your iSCSI storage configuration.

    • Ensure that the iSCSI initiatornames values are correctly configured by using the /etc/iscsi/inititatorname.iscsi file.

    • If you cannot locate errors in the error log, and your iSCSI connections remain disabled, then contact your Network Administrator to confirm that your iSCSI server is functional or to identify network configuration changes.

    • If your network configuration has changed, you must reconfigure your iSCSI connections.

Establish an HA cluster. You must connect your primary HA host with your secondary HA host by using the JSA user interface. For more information about creating an HA cluster, see the Juniper Secure Analytics High Availability Guide.

Troubleshooting ISCSI Issues

To prevent iSCSI disk and communication issues, you must connect JSA, the iSCSI server, and your network switches to an uninterruptible power supply (UPS). Power failure in a network switch might result in your iSCSI volume reporting disk errors or remaining in a read-only state.

In a high-availability (HA) environment, if your primary host fails, you must restore your iSCSI configuration to the primary host. In this situation, the /store or /store/ariel data is already migrated to the iSCSI shared external storage device. Therefore, to restore the primary host iSCSI configuration, ensure that you configure a secondary HA host. For more information, see Configuring iSCSI in an HA Deployment.

  1. Determine whether a disk error exists.
    1. Using SSH, log in to JSA Console as the root user.

    2. Create an empty file filename.txt on your iSCSI volume by typing one of the following command:

      • touch /store/ariel/filename.txt

      • touch /store/filename.txt

    If your iSCSI volume is mounted correctly and you have write permissions to the volume, the touch command creates an empty file that is named filename.txt on your iSCSI volume.

    If you see an error message, unmount and remount the iSCSI volume.

  2. Stop the JSA services.
    • If you migrated the /store file system, type the following commands in the specified order:

      • systemctl stop hostcontext

      • systemctl stop tomcat

      • systemctl stop hostservices

      • systemctl stop systemStabMon

      • systemctl stop crond

    • If you migrated the /store/ariel file system, type the following command:

      systemctl stop hostcontext

  3. Unmount the iSCSI volume.
    • If you migrated the /store file system, type the following commands:

      • umount /store

    • If you migrated the /store/ariel file system, type the following command:

      umount /store/ariel

  4. Mount the iSCSI volume.
    • If you migrated the /store file system, type the following commands:

      mount /store

    • If you migrated the /store/ariel file system, type the following command:

      mount /store/ariel

  5. Test the mount points.
    • If you migrated the /store file system, type the following command:

      touch /store/filename.txt

    • If you migrated the /store/ariel file system, type the following command:

      mount /store/ariel/filename.txt

    If you continue to receive a read-only error message after you remount the disk, then reconfigure your iSCSI volume.

    Alternatively, you can unmount the file system again and run a manual file system check with the following command: fsck /dev/partition .

  6. Start the JSA services.