Table of Contents
Advertisement
● SyncIQ encountered a file system error on the source cluster.
● SyncIQ encountered a file system error on the target cluster.
NOTE:
If you are also experiencing events about hardware failure, investigate the cause of those events before attempting
the following actions.
Administrator action
1. Determine if either the source cluster or the target cluster is in read-only mode by running the following command:
isi readonly
The output for that command displays the mode for each node. If any node is set to read-only mode, set all nodes to
read-write mode by running the following command:
isi_for_array isi readonly off
2. Confirm that the file referenced in the error message exists in the synchronization dataset on the source or target cluster
that encountered the failure and that the files are accessible.
3. Check the SyncIQ logs to see if any error information is available.
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
Gathering cluster
400040018
The SyncIQ policy failed to upgrade.
Description
This event occurs whenever the upgrade sync run for a policy has failed while in progress, or when the source record for the
policy is missing.
Administrator action
Gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to gather cluster logs,
see
Gathering cluster
logs.
400040019
SyncIQ has encountered a problem connecting to a target cluster that is configured in a SyncIQ policy.
Administrator action
1. Confirm that the source cluster can ping the target cluster.
2. Confirm that a traceroute can be completed to the target cluster.
3. Test to confirm that TCP ports 5666, 5667, 2097, 2098, 3147, and 3148 are open on your network by running the following
command from the OneFS command-line interface on either the source or the target cluster:
telnet <IP_address> <port_number>
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
Gathering cluster
72
Software events
logs.
logs.
Advertisement
Table of Contents
