Eyeglass Isilon Alarm Codes

Contents

  1. 1 SCA0001
    1. 1.1 GENERIC_ALARM (Code.SCA0001)
  2. 2 SCA0002
    1. 2.1 INVALID_SRC_DST_CONFIGURATION(Code.SCA0002)
  3. 3 SCA0003
    1. 3.1 INVENTORY_FAILED(Code.SCA0003)
    2. 3.2 REPLICATION_JOB_FAILED(Code.SCA0004)
  4. 4 SCA0005
    1. 4.1 FAILED_TO_CONNECT(Code.SCA0005)
  5. 5 SCA0006
    1. 5.1 BACKUP_JOB_FAILED(Code.SCA0006)
  6. 6 SCA0007
    1. 6.1 JOB_AUDIT_FAILURE(Code.SCA0007)
  7. 7 SCA0008
    1. 7.1 QUOTA_FAILOVER_JOB_FAILED(Code.SCA0008)
  8. 8 SCA0009
    1. 8.1 BASE_LICENSE_TO_EXPIRE(Code.SCA0009)
  9. 9 SCA0010
    1. 9.1 BASE_LICENSE_HAS_EXPIRED(Code.SCA0010)
  10. 10 SCA0011
    1. 10.1 DISCOVERY_LICENSE_TO_EXPIRE(Code.SCA0011)
  11. 11 SCA0012
    1. 11.1 DISCOVERY_LICENSE_HAS_EXPIRED(Code.SCA0012)
  12. 12 SCA0013
    1. 12.1 FEATURE_LICENSE_TO_EXPIRE(Code.SCA0013)
  13. 13 SCA0014
    1. 13.1  FEATURE_LICENSE_HAS_EXPIRED(Code.SCA0014)
  14. 14 SCA0015
    1. 14.1 MANAGEDOBJECT_LICENSE_TO_EXPIRE(Code.SCA0015)
  15. 15 SCA0016
    1. 15.1 MANAGEDOBJECT_LICENSE_HAS_EXPIRED(Code.SCA0016)
  16. 16 SCA0017
    1. 16.1 SUPPORT_LICENSE_TO_EXPIRE(Code.SCA0017)
  17. 17 SCA0018
    1. 17.1 SUPPORT_LICENSE_HAS_EXPIRED(Code.SCA0018)
  18. 18 SCA0019
    1. 18.1 TRIAL_KEY_LIMITS_REACHED(Code.SCA0019)
  19. 19 SCA0020
    1. 19.1 AUDITTRUSTEE_ISSUE(Code.SCA0020)
  20. 20 SCA0021
    1. 20.1   SINGLE_SHARE_MIGRATION_FAILURE(Code.SCA0021)
  21. 21 SCA0022
    1. 21.1   NO_SUPPORT_LICENSE_INSTALLED(Code.SCA0022)
  22. 22 SCA0023
    1. 22.1 REPLICATION_SOURCE_MATCHES_DESTINATION(Code.SCA0023)
  23. 23 SCA0024
    1. 23.1 PREVIOUS_JOB_STILL_RUNNING (Code.SCA0024)
  24. 24 SCA0025
    1. 24.1 NETWORK_ELEMENT_TOO_BUSY(Code.SCA0025)
  25. 25 SCA0026
    1. 25.1 DR_DASHBOARD_STATUS_CHANGE_ALARM (Code.SCA0026)
  26. 26 SCA0027
    1. 26.1 DR_DASHBOARD_STATUS_CHANGE_WARNING (Code.SCA0027)
  27. 27 SCA0028
    1. 27.1 RUNBOOK_ROBOT_JOB_FAILED(Code.SCA0028)
  28. 28 SCA0029
    1. 28.1    POLICY_FAILOVER_FAILURE(Code.SCA0029)
  29. 29 SCA0030
    1. 29.1    ACCESS_ZONE_FAILOVER_FAILURE(Code.SCA0030)
  30. 30 SCA0031
    1. 30.1     DFS_FAILOVER_FAILURE(Code.SCA0031)        
  31. 31 SCA0032
    1. 31.1 READINESS_JOB_FAILED(Code.SCA0032)
  32. 32 SCA0033
    1. 32.1 READINESS_CHECK_ERRORS(Code.SCA0033)
  33. 33 SCA0034
    1. 33.1 SPN_PROCESSING_FAILED(Code.SCA0034)
  34. 34 SCA0035
    1. 34.1   NODE_COUNT_VIOLATION (Code.SCA0035)
  35. 35 SCA0036
    1. 35.1    RUNBOOK_ROBOT_COUNT_EXCEEDED (Code.SCA0036)
  36. 36 SCA0037
    1. 36.1     ACCESS_ZONE_FAILOVER_SPN_FAILURE (Code.SCA0037)
  37. 37 SCA0038
    1. 37.1      POLICY_CONTAINS_EXCLUDES (Code.SCA0038)
  38. 38 SCA0039
    1. 38.1 DISASTER_RECOVERY_TESTING_FAILED(Code.SCA0039)
  39. 39 SCA0040
    1. 39.1 FAILOVER_SUCCEEDED(Code.SCA0040)
  40. 40 SCA0041
    1. 40.1 DISASTER_RECOVERY_TEMPLATE_FAILED(Code.SCA0041)
  41. 41 SCA0042
    1. 41.1 DISASTER_RECOVERY_EDGE_REPLICATION_FAILED(Code.SCA0042)
  42. 42 SCA0043
    1. 42.1 DISASTER_RECOVERY_EDGE_DEPLOYMENT_FAILED(Code.SCA0043)
  43. 43 SCA0044
    1. 43.1 PROBE_UNDER_LICENSED (Code.SCA0044)
  44. 44 SCA0045
    1. 44.1 INVENTORY_DEGRADED(Code.SCA0045)
  45. 45 SCA0047
    1. 45.1 NE_REMOVAL_ERROR(Code.SCA0047)
  46. 46 SCA0046
    1. 46.1 CREATE_SD_EDGE_DEPLOYMENT_JOB(Code.SCA0046) 
  47. 47   SCA0049
    1. 47.1   JOB_AUDIT_WARNING(Code.SCA0049) 
  48. 48 SCA0050  
    1. 48.1   QUOTA_INVENTORY_FAILED(Code.SCA0050) 
  49. 49 SCA0051  
    1. 49.1   DEDUPE_REPLICATION_FAILED(Code.SCA0051) 
  50. 50 SCA0052
    1. 50.1   DUPLICATE_INVENTORY_ITEM(Code.SCA0052) 
  51. 51 SCA0053
    1. 51.1   CONTINUOUS_OPERATION_STATUS_ERROR(Code.SCA0053) 
  52. 52 SCA0054
    1. 52.1   MIGRATION_JOB_SUCCEEDED(Code.SCA0054) 
  53. 53 SCA0055
    1. 53.1   ARCHIVE_UPLOAD_FAILED(Code.SCA0055) 
  54. 54 SCA0056
    1. 54.1   DEDUPE_AUDIT_FAILED(Code.SCA0056) 
  55. 55 SCA0057
    1. 55.1 QUOTA_SYNCHRONIZATION_FAILED(Code.SCA0057) 
  56. 56 SCA0058
    1. 56.1   ERROR_RETRIEVING_CLUSTER_VERSION(Code.SCA0058) 
  57. 57 SCA0059
    1. 57.1   RANSOMWARE_DEFENDER_UNDER_LICENSED(Code.SCA0059) 
  58. 58 SCA0060
    1. 58.1   ERROR_GENERATING_DATASET(Code.SCA0060) 
  59. 59 SCA0061
    1. 59.1   RANSOMWARE_DEFENDER_EVENT(Code.SCA0061) 
  60. 60 SCA0062
    1. 60.1   RANSOMWARE_USER_LOCKED(Code.SCA0062) 
  61. 61 SCA0063
    1. 61.1   RANSOMWARE_USER_LOCK_FAILED(Code.SCA0063)
  62. 62 SCA0064
    1. 62.1   RANSOMWARE_ECA_IGLS_SERVICE_FAILURE(Code.SCA0064) 
  63. 63 SCA0065
    1. 63.1   RANSOMWARE_ECA_HBASE_FAILURE(Code.SCA0065) 
  64. 64 SCA0066
    1. 64.1   RANSOMWARE_ECA_COMM_FAILURE(Code.SCA0066) 
  65. 65 SCA0067
    1. 65.1   RANSOMWARE_NODE_FAILURE(Code.SCA0067) 
  66. 66 SCA0068
    1. 66.1   RANSOMWARE_ENTER_MONITOR_MODE(Code.SCA0068) {
  67. 67 SCA0069
    1. 67.1   RANSOMWARE_LEAVE_MONITOR_MODE(Code.SCA0069)
  68. 68 SCA0070
    1. 68.1   RANSOMWARE_ECA_VERSION(Code.SCA0070)
  69. 69 SCA0071
    1. 69.1   SECURITY_GUARD_FAILURE(Code.SCA0071) 

SCA0001

GENERIC_ALARM (Code.SCA0001)

description = "Error within the SCA service.";

severity = AlarmSeverity.CRITICAL;


Help on this Alarm:  

This covers all unknown errors that have no more specific errors.

SCA0002

INVALID_SRC_DST_CONFIGURATION(Code.SCA0002)

description = "Found a replication job where either the source or destination is not a managed network element.";

severity = AlarmSeverity.CRITICAL;


Help on this Alarm:  

  • Problem: This alarm will occur when an Eyeglass configuration replication Job fails to run because is associated with an Isilon cluster that has not been provisioned in Eyeglass. The  Eyeglass configuration replication Jobs are created based on the SyncIQ policies discovered during the Eyeglass Inventory task.  It is possible that an Isilon cluster provisioned in Eyeglass could have SyncIQ policies that have Isilon cluster targets that are not provisioned in Eyeglass.

  • Resolution:

    • Provision Eyeglass with all Isilon clusters related to Eyeglass configuration replication Jobs

    • If not all Isilon clusters associated with Eyeglass configuration replication Jobs can be managed by Eyeglass, disable Eyeglass configuration replication Jobs associated with Isilon clusters not managed by Eyeglass to avoid the error

SCA0003

INVENTORY_FAILED(Code.SCA0003)

description = "Failed to retrieve inventory.";

severity = AlarmSeverity.CRITICAL;

Help on this Alarm:   

  • Problem: This alarm will occur when the Eyeglass Inventory task which discovers the configuration information on an Isilon cluster has failed to run.

  • Resolution:

    • Ensure that Isilon clusters are reachable from Eyeglass server

    • This problem can also occur if the Inventory task attempts to start while another instance of the Inventory task is still running.  In this case the problem will be transient and will clear on it's own.  If this problem persists, contact support.superna.net for assistance.

    • If the Info for the alarm shows “Error fetching data from ssh.  Inventory may be incomplete” there is an issue with retrieving the Inventory information that requires ssh access.  This may be a problem with the permissions of the Isilon cluster user in Eyeglass.  Check the following

      • Ensure that the Isilon cluster user role in Eyeglass has Network Read/Write permissions

      • Ensure that the Isilon cluster user roled in Eyeglass does not contain a - or other special characters.  This can cause an issue with the sudo command that is used.  To troubleshoot this condition:

  1. Login to Isilon cluster CLI as Isilon Cluster user that has been provisioned in Eyeglass

  2. Execute the command below – it needs to be able to execute without error

sudo isi networks list pools


Example of successful command execution


% sudo isi networks list pools

Subnet          Pool         SmartConnect Zone                   Ranges Alloc

--------------- --------------- ---------------------- ---------------------- -------

int-a-subnet    int-a-pool                             192.168.4.145-192.1... Static



Example of failed command execution


sudo isi networks list pools

sudo: >>> /usr/local/etc/sudoers: syntax error near line 168 <<<

sudo: parse error in /usr/local/etc/sudoers near line 168

sudo: no valid sudoers sources found, quitting

sudo: unable to initialize policy plugin



REPLICATION_JOB_FAILED(Code.SCA0004)

NOTE: failure for any property of a share, export or quota to replicate will stop all replication for that share/export/quota.

description = "Replication job failed to run.";

severity = AlarmSeverity.CRITICAL;

Help on this Alarm:  


Following reasons are commonly seen to cause a replication job failure.  The Info related to the alarm should be verified to confirm the cause:

  • AEC_NOT_FOUND  Zone <Zone Name> not found.    

    • Problem: This error is issued when the Eyeglass configuration replication job runs and attempts to replicate a share or export when the associated Zone does not exist on the target.

    • Resolution: Ensure that all Zones associated with shares and exports exist on the target.  Once the Zones exist, the next configuration replication job will succeed and the alarm will be cleared

  • AEC_NOT_FOUND  "Path 'x/y/z' not found: No such file or directory".    

    • Problem: This error is issued when the Eyeglass configuration replication job runs and attempts to replicate a share or export or quota when the associated directory does not exist on the target.

    • Possible Cause for Missing Path (Group 1):

      • SyncQ Policy associated with the path has not been run.

      • Path is on the SyncIQ Policy Excluded list.

      • SyncIQ Policy has paths in the included or excluded list and the path that was not found is protected by the policy but is not in either list.

    • Resolution (Group 1): Ensure that all directories associated with shares and exports and quotas exist on the target.  Once the Zones exist, the next configuration replication job will succeed and the alarm will be cleared

    • Possible Cause for Missing Path (Group 2):

      • share path has a trailing "/" at the end of the share path - example /ifs/home/
    • Resolution (Group 2): We recommend to remove the trailing "/" from the path of the share to resolve the error.
  • AEC_EXCEPTION bad hostname <host name>

    • NFS Export Clients field has a host name entry that cannot be resolved on replication of the Export

  • AEC_EXCEPTION Cannot set security descriptor on <share path> Read only file system
    • You will receive the above error when Eyeglass is not able to sync share properties such as ABE (Access based Enumeration).
    • In this case we recommend you to compare all properties of the active cluster share with the target cluster share and make it identical with the source.


SCA0005

FAILED_TO_CONNECT(Code.SCA0005)

description = "Failed to connect to the designated target.";

severity = AlarmSeverity.CRITICAL;

Help on this Alarm:    

  • Problem: This alarm will occur when Eyeglass cannot establish a connection with an Isilon cluster it is managing.

  • Resolution:

    • Verify that there have been no change in Isilon credentials which would cause Eyeglass provisioning to be out of date.

    • Verify that there have been no networking or firewall changes which would result in loss of network connectivity between the Eyeglass server and the Isilon clusters.


SCA0006


BACKUP_JOB_FAILED(Code.SCA0006)


description = "Failed to create a backup archive.";

severity = AlarmSeverity.MAJOR;


   

Help on this Alarm:      


SCA0007

JOB_AUDIT_FAILURE(Code.SCA0007)

   

           

           description = "Replication job audit failed.";

           severity = AlarmSeverity.MAJOR;


   

Help on this Alarm:    

  • Problem: The Eyeglass audit task compares source and destination configuration items post replication to confirm that the replication task has done it's Job and that the configuration items on the source and target are indeed identical. Replication job audit failed alarm will occur when:

    • audit job fails to run

    • audit job finds configuration item where source and target are different

  • Resolution:  Use the Info related to the alarm aid in resolving the issue

    • audit job failure to run

      • Info: Audit of shares for current job is inconclusive because source and target network element are identical.

      • Resolution: Eyeglass configuration replication Job has same Isilon cluster configured as source and target.  Eyeglass cannot perform replication configuration or the associated audit with this configuration. Disable this Job to avoid this alarm.

  • Info: Audit of job 'xxx' has failed: Source and/or target network element were not found in provided list of network elements

  • Resolution: Source and target Isilon Clusters in Job xxx must be managed by Eyeglass for audit to run.

  • audit job finds configuration item where source and target are different

    • Info: Audit failed: Values for key 'xxx' do not match: source: share or export  ; target: share or export

      • key 'xxx' refers to a property of share or export where mismatch was found

    • Info: Auditable source (type: 'xxx', zone: 'yyy', name: 'zzz') and target (type: 'xxx', zone: 'yyy', name: 'zzz') objects not found on source or target cluster, hence audit fails.

      • Auditable source refers to configuration item

    • Resolution:

      • Check that associated Replication Job was successfully run.  If not, source and destination may indeed be different. and Replication Job issue needs to be resolved.

      • It is possible that a change to configuration item was made via OneFS after replication Job completed and before audit task ran.  The next replication task will resolve this mismatch.


SCA0008


QUOTA_FAILOVER_JOB_FAILED(Code.SCA0008)

           

           description = "Quota failover job failed.";

           severity = AlarmSeverity.CRITICAL;



Help on this Alarm:  

   


SCA0009

BASE_LICENSE_TO_EXPIRE(Code.SCA0009)

   

       protected AlarmData create(String syncKey, String extraInfo) {

           

           description = "Base license to expire.";

           severity = AlarmSeverity.WARNING;


 

       

Help on this Alarm:  

Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0010

BASE_LICENSE_HAS_EXPIRED(Code.SCA0010)


               description = "Base license has expired.";

               severity = AlarmSeverity.MAJOR;



Help on this Alarm:  

   Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0011

DISCOVERY_LICENSE_TO_EXPIRE(Code.SCA0011)


           

           description = "Discovery license to expire.";

           severity = AlarmSeverity.WARNING;


Help on this Alarm:  

       Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0012

DISCOVERY_LICENSE_HAS_EXPIRED(Code.SCA0012)


               

               description = "Discovery license has expired.";

               severity = AlarmSeverity.MAJOR;



Help on this Alarm:  

   Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0013

FEATURE_LICENSE_TO_EXPIRE(Code.SCA0013)


           

           description = "Feature license to expire.";

           severity = AlarmSeverity.WARNING;



Help on this Alarm:  


Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.


SCA0014

 FEATURE_LICENSE_HAS_EXPIRED(Code.SCA0014)


               

               description = "Feature license has expired.";

               severity = AlarmSeverity.MAJOR;


   },

Help on this Alarm:  

   Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0015

MANAGEDOBJECT_LICENSE_TO_EXPIRE(Code.SCA0015)


           

           description = "Managed object license to expire.";

           severity = AlarmSeverity.WARNING;



Help on this Alarm:  

       Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0016

MANAGEDOBJECT_LICENSE_HAS_EXPIRED(Code.SCA0016)


               description = "Managed object license has expired.";

               severity = AlarmSeverity.MAJOR;



Help on this Alarm:  

   Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0017

SUPPORT_LICENSE_TO_EXPIRE(Code.SCA0017)


           

           description = "Support license to expire.";

           severity = AlarmSeverity.WARNING;



Help on this Alarm:  

       Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0018

SUPPORT_LICENSE_HAS_EXPIRED(Code.SCA0018)


               

               description = "Support license has expired.";

               severity = AlarmSeverity.MAJOR;



Help on this Alarm:  

   Trial key has expired and can be renewed on the support.superna.net site by opening a case with your appliance id.

SCA0019

TRIAL_KEY_LIMITS_REACHED(Code.SCA0019)


           

           description = "Replication functionality limited by trial. ";

           severity = AlarmSeverity.WARNING;



Help on this Alarm:  

   The trial key has limits applied.  Open a case on support.superna.net to request higher limits.

SCA0020

AUDITTRUSTEE_ISSUE(Code.SCA0020)

           

        description = "Replication audit issue with trustee(s).";

        severity = AlarmSeverity.CRITICAL;



Help on this Alarm:  


SCA0021

  SINGLE_SHARE_MIGRATION_FAILURE(Code.SCA0021)


           

           description = "Single Share Migration Job failed.";

           severity = AlarmSeverity.MAJOR;



Help on this Alarm:  

The migration job has encountered an error, this error code relates to folder migration feature.  The SyncIQ policy and migration job from running jobs window should be checked for the failed step and find the info button for the error to raise a case with support.


SCA0022

  NO_SUPPORT_LICENSE_INSTALLED(Code.SCA0022)


           

           description = "No support license has been installed; " +

             "patches cannot be applied.";

           severity = AlarmSeverity.MAJOR;


  

Help on this Alarm:  

This indicates no support license key is installed which is required to raise a case for a production appliance.  If you support keys have expired a new order is required to purchase a new support contract.

SCA0023

REPLICATION_SOURCE_MATCHES_DESTINATION(Code.SCA0023)


           

           description = Found a replication job where the source and " +

                         "destination are the same and that replicates shares.";

           severity = AlarmSeverity.CRITICAL;


  

Help on this Alarm:  

This alarm is expected if a SyncIQ Job is discovered where the source and target refer to the same cluster.

SCA0024

PREVIOUS_JOB_STILL_RUNNING (Code.SCA0024)


           

           description = "A scheduled task was unable to run as there was another instance already running.";

           severity = AlarmSeverity.WARNING;

Help on this Alarm:  

This alarm will occur when there is a replication task in progress at the time when a new replication task is scheduled to begin.  By default, Eyeglass attempts to begin a new replication task every 5 minutes.  In the event that configuration replication takes longer than 5 minutes on your Eyeglass system you will see this alarm for each attempt to start replication that was blocked.

No action is required.  When the in-progress configuration replication Job completes, the next scheduled configuration replication task will begin.

SCA0025

NETWORK_ELEMENT_TOO_BUSY(Code.SCA0025)

    

       protected AlarmData create(String syncKey, String extraInfo)

           

description = "The target is too busy to respond to all requests. " +

 "Consider reducing the number of parallel operations.";

severity = AlarmSeverity.MAJOR;


 

Help on this Alarm:  

This alarm will occur when the API call to the cluster returns this error.   It indicates the cluster node is busy and is refusing to answer API calls.  This can happen if too many parallel operations are issued to the cluster using PAPI.  No arm will occur in this condition but Eyeglass can not complete the operation and will generate other errors.  This can also occur on a heavily used cluster or a node in the cluster that has resource issues i.e. CPU utilization.


To correct this operation  raise a support request to get instructions to reduce the number of parallel API calls used to connect to a cluster.  

  



SCA0026

DR_DASHBOARD_STATUS_CHANGE_ALARM (Code.SCA0026)


           

           description = "The job status for the job changed to error";

           severity = AlarmSeverity.CRITICAL;


  

Help on this Alarm:  

This alarm will occur when there is an error state either on a Configuration Replication Job or on a SyncIQ Policy Job resulting in an overall DR Dashboard status related to that policy to be in Error.

To troubleshoot this error, login to the Eyeglass web page and open the DR Dashboard window.  Find the Job which was reporting an error and expand it to determine whether the issue is with the SyncIQ policy Job or the Eyeglass Configuration Replication Job.  If the problem lies with the SyncIQ Job, further troubleshooting should be done from OneFS.  If the problem lies with Eyeglass Configuration Replication Job, open the Alarms window and look for an alarm which has this Configuration Replication Job as the source.  The Info of this alarm will provide additional details regarding the cause of the issue.


SCA0027

DR_DASHBOARD_STATUS_CHANGE_WARNING (Code.SCA0027)


           

           description = "The job status for the job changed to either 'pending' or 'disabled'";

           severity = AlarmSeverity.WARNING;


  

Help on this Alarm:  

This alarm will occur when there is a DR Dashboard status change for a Job to either Pending or Disabled.

For a status of Pending, no action is required.  This is an indication that the Job has not yet been run.

For a status of Disabled, this status may occur if the SyncIQ Policy has been disabled in OneFS or if the Configuration Replication Job has been User Disabled in Eyeglass. If Disabled is not the correct status for this Job, login to the Eyeglass web page and open the DR Dashboard window.  Expand the Job related to the alarm to determine whether the SyncIQ Policy has been disabled or the Eyeglass Configuration Replication Job.  If this Job should not be disabled for the SyncIQ policy you must enable using the OneFS interface.  For Eyeglass Configuration Replication, open the Jobs window and then select the Job in the list.  Open the Select a bulk action menu and select Enable/Disable.

SCA0028

RUNBOOK_ROBOT_JOB_FAILED(Code.SCA0028)

      

   

           description = "The Runbook Robot job failed for job: "

           severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm will occur when the run book robot job fails and indicates you have misconfigured the robot or the robot failed and your cluster is not ready for a real DR event.  The robot is the best indication of readiness for failover.  

SCA0029

   POLICY_FAILOVER_FAILURE(Code.SCA0029)

           

           description = "Policy Failover Job failed.";

           severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm will occur when a DR Assistant failover job has been created and submitted to failover a policy.  To recover from this alarm.  Open the DR Assistant icon on the Eyeglass desktop and select the failover history.  Review the failover log for the failover job to find which step in the failover did not complete so you know where to begin manual step recovery.  Use the Failover Recovery Guide for guidance on manual recovery.    


SCA0030

   ACCESS_ZONE_FAILOVER_FAILURE(Code.SCA0030)

            description = "Access Zone Failover Job failed.";

           severity = AlarmSeverity.MAJOR;


Help on this Alarm:  

This alarm will occur when a DR Assistant failover job has been created and submitted to failover an Access zone.  To recover from this alarm.  Open the DR Assistant icon on the Eyeglass desktop and select the failover history.  Review the failover log for the failover job to find which step in the failover did not complete so you know where to begin manual step recovery.  Use the Failover Recovery Guide for guidance on manual recovery.   


SCA0031

    DFS_FAILOVER_FAILURE(Code.SCA0031)        

           description = "DFS Failover Job failed."

           severity = AlarmSeverity.MAJOR


          

Help on this Alarm:  

This alarm will occur when a DR Assistant failover of a DFS job has failed. The DR Assistant history window has a log that should be reviewed for which step failed and take corrective action from when the failure occured to manually recover the failed steps.  Use the Failover Recovery Guide for guidance on manual recovery..


SCA0032

READINESS_JOB_FAILED(Code.SCA0032)

     description = "Readiness job failed to run."

     severity = AlarmSeverity.MAJOR


Help on this Alarm:  

The Failover Readiness job encountered unexpected errors when running.  Run Failover Readiness manually from the Eyeglass Jobs window.  Ensure the Access Zone Prerequisites have been meet.


SCA0033

READINESS_CHECK_ERRORS(Code.SCA0033)

     description = "Readiness job execution found errors - not ready " +

 "for failover.";

      severity = AlarmSeverity.CRITICAL;

Help on this Alarm:  

This alarm will occur when a Zone readiness job that check various parameters, settings, mappings for Smartconnect Zones, SPN values on cluster machine accounts are not registered with the AD.  This requires delegation steps to SPN property on the machine account and should be check first in documentation the procedures.   Network mapping not completed is another reason the readiness job can fail.   It will also be failed if SyncIQ job associated with the Zone has failed (based on its path and access zone root path),  if configuration replication also fails for any policy in an Access zone this will also trigger a zone readiness failure.


Go to the Eyeglass DR Dashboard Zone Readiness tab and select the zone name to check the status.  Click mapping to verify all hints are in place, then click status make sure its green if not look for the failed item in the list and take action to resolve either SyncIQ failures,  configuration replication job failures and policies and SPN failures.


SCA0034

SPN_PROCESSING_FAILED(Code.SCA0034)

                    description = "SPN processing (either checking or repairing) has failed.";

                    severity = AlarmSeverity.MAJOR

                   

Help on this Alarm:  

This alarm will occur when Eyeglass was unable to create or delete SPNs during the regular Inventory task.  Manually inspect existing SPNs using the ADSI Edit tool and ensure that there is an SPN for each Smartconnect Zone and Smartconnect Zone alias used for SMB share access.  Make sure delegation is done correctly

SCA0035

  NODE_COUNT_VIOLATION (Code.SCA0035)

description = "The node count limitation has been exceeded."

severity = AlarmSeverity.CRITICAL

Help on this Alarm:  

This alarm will occur when you have an Eyeglass Node based license (License Type SEL EYEGLASS DR MANAGER ADVANCED  OR Ent VAPP in the Eyeglass Managed Licenses window) and the number of nodes in the Isilon clusters being managed by Eyeglass exceeds the number of nodes that you have licensed.  Additional node licenses must be purchased to match the total number of managed nodes.  No product support is provided for under licensed clusters.


SCA0036

   RUNBOOK_ROBOT_COUNT_EXCEEDED (Code.SCA0036)

description = "The runbook robot job count has been exceeded."

severity = AlarmSeverity.WARNING

Help on this Alarm:  

This alarm will occur to inform you that you have configured more than one Eyeglass Runbook Robot job on the Isilon clusters being managed by Eyeglass.  Eyeglass will only execute one Runbook Robot job.  Remove extra Runbook Robot jobs by deleting the SyncIQ policies with the special name and ensure only 1 exists.


SCA0037

    ACCESS_ZONE_FAILOVER_SPN_FAILURE (Code.SCA0037)

description = "Failed to delete or repair SPNs during failover"

severity = AlarmSeverity.CRITICAL

Help on this Alarm:  

This alarm will occur when Eyeglass was unable to create or delete SPNs related to Smartconnect Zone changes that were made during an Access Zone failover.  Manually inspect existing SPNs using the ADSI Edit tool:

  1. Failover Source Cluster - SPN for SmartConnect Zone that is prefixed with “igls-original” does NOT exist.  

  2. Failover Target Cluster - SPN for SmartConnect Zone Alias added during failover DOES exist.


Where the above conditions are not met, using ADSI Edit to update SPN to be on correct cluster.  You cannot create a missing SPN on the Active Cluster if it still exists for the Failed Over cluster.  You need to remove from Failover Over cluster first and then add to active cluster.  Make sure delegation is done correctly

SCA0038

     POLICY_CONTAINS_EXCLUDES (Code.SCA0038)

description = "Found a policy with excluded directories.  This is not a supported SyncIQ configuration for failback."

severity = AlarmSeverity.WARNING

Help on this Alarm:  

This alarm will occur to inform you that Eyeglass has detected a SyncIQ Policy with excludes (or includes) configured.  This is not a supported SyncIQ configuration for failback.”

SCA0039

DISASTER_RECOVERY_TESTING_FAILED(Code.SCA0039)

description = "The disaster recovery testing has failed.";
severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm will occur when Eyeglass has executed DR test mode job and it resulted in an error, retry the enable or disable or check the running jobs window for details on the failover.

SCA0040

FAILOVER_SUCCEEDED(Code.SCA0040)

description = "Failover Succeded";
severity = AlarmSeverity.INFORMATIONAL;

Help on this Alarm:  

This alarm will occur when Eyeglass has successfully executed any failover mode without error and is sent to log that a failover has occured.

SCA0041

DISASTER_RECOVERY_TEMPLATE_FAILED(Code.SCA0041)

description = "The disaster recovery Template Replication has failed.";
severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm will occur when Eyeglass IsilonSD product has deployed an access zone template to an edge cluster and the job has failed. Check the running job for specific error or step that failed before retrying again.


SCA0042

DISASTER_RECOVERY_EDGE_REPLICATION_FAILED(Code.SCA0042)

description = "The disaster recovery Replication to SD Edge has failed.";
severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm will occur when Eyeglass IsilonSD edition has executed failover from the core to the edge cluster and resulted in failure to setup the edge site after configuring failover. Consult the running jobs window for specific error and step before attempting to retry the job.

SCA0043

DISASTER_RECOVERY_EDGE_DEPLOYMENT_FAILED(Code.SCA0043)

description = "The disaster recovery Deployment to SD Edge has failed.";
severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm will occur when Eyeglass IsilonSD edition product deploys the core access zone template and syncs shares and exports to the edge cluster. This setup requires policies to sync folder structure before shares and exports can be created. Check policy run status on the Isilon and running jobs window to verify the step and error code that blocked the job from completing before retrying the job.


SCA0044

PROBE_UNDER_LICENSED (Code.SCA0044)

description = "The Probe is under-licensed."; severity = AlarmSeverity.MAJOR;

Help on this Alarm:  

This alarm indicates more clusters are managed by eyeglass DR than eyeglass CA UIM Probe license keys installed. Eyeglass will randomly select which clusters are managed for the CA UIM alarm monitoring. contact sales@superna.net to get a quote on additional probe license keys to remove the alarm and get a fully supported installation.

SCA0045

INVENTORY_DEGRADED(Code.SCA0045)

description = "Inventory is degraded/incomplete"; severity = AlarmSeverity.MINOR;

Help on this Alarm:  

This alarm indicates the inventory process that runs when cluster configuration replication job runs (default 5 minute intervals), encountered API failure responses from the cluster node the API request was sent too. This condition can clear on its own if the cluster node resumes processing API REST calls. If the configuration replication job fails completely then the cluster has stopped answering API calls. It is best to monitor how often this alarm is seen, and IF persistent open a case with support and upload the logs to the case. The logs will be requested if not attached to the case. If the condition persists EMC support case should be opened, as the node is overloaded and unable to respond to API queries. NOTE: The OneFS UI also uses the REST API and ignoring this event can affect OneFS UI on the node that is returning the API failures.


SCA0047

NE_REMOVAL_ERROR(Code.SCA0047)

description = "Network element removal failed"; severity = AlarmSeverity.CRITICAL; Help on this Alarm:  

This alarm is raised and logged when a cluster previously under management has been deleted which is a user action.  This alarm will never be generated without manual delete from the Inventory Icon on the eyeglass desktop.   If this alarm is unexpected, it indicates someone deleted the cluster and re-added it.  This is not a recommended procedure for any errors encountered with eyeglass.  Unless you know what procedure you are doing, check with support before deleting a cluster from inventory when active DR monitoring in production is the current state for this cluster.    Test clusters can be deleted if needed using this procedure.

1. Open Inventory Window

2. Select Cluster

3. Right click and select Delete NE


SCA0046

CREATE_SD_EDGE_DEPLOYMENT_JOB(Code.SCA0046) 

      description = "Creation of SD Edge deployment Job failed";

      severity = AlarmSeverity.MINOR;

    Help on this Alarm:  

This alarm only applies to the Branch office config and data protection licensed solution. when building a new edge site the deployment job failed.

  1. This can be caused by un-reachable cluster
  2. SyncIQ command failed to return with a status code from the cluster
  3. Timeout waiting on a cluster command to complete.  Check syncIQ reports for the temporary deployment policy that Eyeglass creates to look for errors on the source cluster where the template access zone was created.


  SCA0049

  JOB_AUDIT_WARNING(Code.SCA0049) 

    


      description = "Replication job audit resulted in a warning";

      severity = AlarmSeverity.WARNING;


  Help on this Alarm:  

      This alarm is raised when the cluster sync audit step runs as per of configuration replication job.  This step gets inventory from both clusters and does a share,export,quota, snapshot schedule, dedupe setting, nfs aliases object and Attribute comparison.  This generally indicates the source cluster policy and target cluster policy configuration data is not 100% in sync.  The error in the alarms window includes an info text that will describe the field or objects that are not an exact match.

Resolution will require checking with support on the error to determine resolution.  

It is possible that target cluster defaults for shares,exports are set in a way that means synced shares or exports by Eyeglass get modified by the target cluster to apply cluster defaults that are different from the source cluster. This can cause an attribute to change that the audit will detect.  

The first place to check is default settings on both clusters match for shares and exports.

It is also possible someone manually changed a setting on a share or export on the target cluster causing the audit to fail.

In general we recommend that both source and target clusters are exact matches.

SCA0050  

  QUOTA_INVENTORY_FAILED(Code.SCA0050) 

  

      description = "Failed to retrieve quotas";

      severity = AlarmSeverity.CRITICAL;

 Help on this Alarm:  

The quotas are retrieved with REST api calls pages at a time.  On clusters with 1000's or 10 000's of thousands of quotas, this process requires many api calls to complete to collect each quota and any notifications setup for each quota (retrieved with separate API calls).  If an API call fails while retrieving quotas through this long running multi query part of the Configuration Sync job, this error can be returned.

This could also happen if eyeglass minimum permissions where not set correctly and should be checked.


SCA0051  

  DEDUPE_REPLICATION_FAILED(Code.SCA0051) 

    

      description = "Deduplication replication job failed to run";

      severity = AlarmSeverity.MAJOR;


Help on this Alarm:      

As of Eyeglass 1.6.3 and later dedupe paths are synced between clusters , configuration replication jobs are responsible for syncing dedupe paths  and if an API failure to set all the paths on the target cluster occurs this alarm is raised.  This could be minimum permissions issue with the eyeglass service account or API failure and configuration replication in running jobs should be expanded to find the info text that identifies the API error that triggered the failure.  Search documentation site on how to find and identify sync errors.


SCA0052

  DUPLICATE_INVENTORY_ITEM(Code.SCA0052) 

    

      

      description = "Found duplicate inventory items.";

      severity = AlarmSeverity.MAJOR;

      Help on this Alarm:      

This error is raised when inventory function that runs as part of configuration job, identifies two entries that are duplicate and cannot be saved to the database.  Raise a support case if this error is seen on instructions on how to reset the database to remove duplicate items.  The database in 1.7.0 and later can be rediscovered safely with all job settings being discovered.


SCA0053

  CONTINUOUS_OPERATION_STATUS_ERROR(Code.SCA0053) 

    

      description = "Continuous operation status is ERROR";

      severity = AlarmSeverity.MAJOR;


Help on this Alarm:     

The new continuous operations dashboard shows the overall status of Snapshot sync and dedupe sync status, if this dashboard and status can not be updated from the configuration sync jobs or if sync status failed on SyncIQ policies paths with snapshot schedules or dedupe path settings related to SyncIQ jobs are not in Sync on source and target cluster,  this alarm is raised indicate Readiness for operations on the target cluster is impacted.


Review the dashboard to identify the policy that is affected, which will help identify which area snapshots or dedupe are in sync error state. This can be done using the running jobs window and expanding the last errored job to find the policy and section for snapshot schedule and dedupe sync to identify the API error that is the root cause of the dashboard state change to error state. Search documentation site on how to find and identify sync errors.


SCA0054

  MIGRATION_JOB_SUCCEEDED(Code.SCA0054) 

    


      description = "Migration job succeeded.";

      severity = AlarmSeverity.INFORMATIONAL;

Help on this Alarm:    

This indicates an Access Zone Migration job has completed successfully.


SCA0055

  ARCHIVE_UPLOAD_FAILED(Code.SCA0055) 

         

      description = "Archive upload failed";

      severity = AlarmSeverity.CRITICAL;

      

Help on this Alarm:   

The new about Eyeglass --> backup tab now has upload directly to support option for logs, this error indicates the upload failed. Which is likely caused by firewall blocking the Eyeglass appliance from directly reaching the support portal to upload the log.

If you see this error it means support did not get the log file and you should login to the support site download the backup archive and upload manually to the support site.  The direct upload requires port 443 HTTPS directly to the Internet from the  Eyeglass appliance.


SCA0056

  DEDUPE_AUDIT_FAILED(Code.SCA0056) 

    

      description = "Deduplication audit job failed to run";

      severity = AlarmSeverity.MAJOR;


Help on this Alarm:   


This indicates the audit of both clusters dedupe settings (run automatically for the configuration sync jobs), was not able to complete the comparison between the cluster.  Run manually again and see if the error persists.   If the error is still present then open a case with support.


SCA0057

QUOTA_SYNCHRONIZATION_FAILED(Code.SCA0057) 

    
   

      description = "Quota Synchronization Job Failed";
      severity = AlarmSeverity.MAJOR;


Help on this Alarm:   

When a quota job run during failover or manual (should not be run manually).  An error can occur if the cluster returns a create or delete quota error.  This is most common when a domain lock from a quota scan blocks quota create API's.   Unlinked Everyone quotas can also cause quota create or delete to fail.  Use the info text in the running jobs screen to collect the error code and submit a case to Support.

SCA0058


  ERROR_RETRIEVING_CLUSTER_VERSION(Code.SCA0058) 



      description = "Error retrieving cluster version.";
      severity = AlarmSeverity.MAJOR;



Help on this Alarm:   

This error occurs when a heartbeat task checks the cluster Onefs version and the api fails.  This is commonly seen when a cluster was upgraded to Onefs 8 but the SCA process was not restarted afterwards.  This document explains steps needed when a cluster major version from 7 to 8 is completed and how to have Eyeglass detect the new cluster version.  Guide here.

SCA0059


  RANSOMWARE_DEFENDER_UNDER_LICENSED(Code.SCA0059) 



      description = "The Ransomware Defender is under-licensed.";
      severity = AlarmSeverity.MAJOR;


Help on this Alarm:   

This alarm will be raised when Eyeglass has more licenses and clusters added than Ransomware agent license installed.  Each monitored cluster requires an agent license.  Contact sales@superna.net to get a quote for agent licenses.


SCA0060


  ERROR_GENERATING_DATASET(Code.SCA0060) 


      description = "Error generating data sets.";
      severity = AlarmSeverity.MINOR;


Help on this Alarm:   

This alarm is raised when the servicenow integration api tries to build a data set that is exposed via an xml url https://eyeglass ip address/servicenow/servicenow.xml.  This error would occur if not all API data is available to generate the dataset and expose through the xml interface.  This does not affect DR functionality and can be ignored if you are not using this feature.

SCA0061

  RANSOMWARE_DEFENDER_EVENT(Code.SCA0061) 


      description = "Ransomware signal received.";
      severity = AlarmSeverity.CRITICAL;



Help on this Alarm:   

This alarm is raised for each security event raised for a user.   This should be reviewed in the active events tab of the ransomware defender icon to determine shares affected or lock out status for this event.    Actions possible are lockout, recover, initiate self recovery option.

SCA0062


  RANSOMWARE_USER_LOCKED(Code.SCA0062) 


      description = "Locked user access.";
      severity = AlarmSeverity.CRITICAL;



Help on this Alarm:   

A user was locked out with a Major or Critical detection security event.  Consult the Ransomware defender GUI to identify the user ID, IP address of the machine where the user was logged in.   Files affected can be exported to a CSV to inspect and remediate comprised files.    The data recovery initiated  option can be used to recover files from DR and snapshots.  The user can be restored using the restore user access option.

SCA0063


  RANSOMWARE_USER_LOCK_FAILED(Code.SCA0063)


      description = "Failed to lock user access after ransomware events received.";
      severity = AlarmSeverity.CRITICAL;



Help on this Alarm:   

A lock of a user account was not successful, consult the log for the action menu to see which shares or clusters the lockout job failed.  This indicates these shares are not locked out for this user and manual lockout of the share for the affected user should be done.  The lockout is not retried.  It can be retried from the actions menu.

SCA0064


  RANSOMWARE_ECA_IGLS_SERVICE_FAILURE(Code.SCA0064) 


      description = "ECA Service not forwarding all security events";
      severity = AlarmSeverity.MAJOR;



Help on this Alarm:   

One or more nodes on an ECA cluster are not successfully communicating with the Eyeglass appliance. Click on the Manage Services icon on the Eyeglass desktop, and use the status of each ECA node and it's subcomponents to determine which ECA node is unhealthy.  

SCA0065



  RANSOMWARE_ECA_HBASE_FAILURE(Code.SCA0065) 


      description = "ECA Service not scanning Hbase for events";
      severity = AlarmSeverity.MAJOR;





Help on this Alarm:   

If the alarm in SCA0064 is raised, eyeglass will attempt to periodically scan the ransomware signals database for new signals. If this scanning cannot happen, this alarm will be raised. To resolve: restore eyeglass to hbase connectivity. 

SCA0066



  RANSOMWARE_ECA_COMM_FAILURE(Code.SCA0066) 


      description = "ECA Service unreachable to scan for events";
      severity = AlarmSeverity.MAJOR;


  

Help on this Alarm:   


The Eyeglass VM cannot reach the ECA cluster to scan the analytics database.  This impacts detection of Ransomware events.  This should be fixed and look at networking and ecactl CLI commands in ransomware admin guide for troubleshooting.

SCA0067



  RANSOMWARE_NODE_FAILURE(Code.SCA0067) 

      description = "ECA Node inactive or in error state";
      severity = AlarmSeverity.MAJOR;


Help on this Alarm:   

An ECA cluster node has stopped sending alive heartbeats to the eyeglass VM. The ECA cluster is now in a degraded state until the node is fixed.  See the admin guide on steps to login to the node and check services and container health.

SCA0068


  RANSOMWARE_ENTER_MONITOR_MODE(Code.SCA0068) {


      description = "Ransomware: Entered monitor only mode";
      severity = AlarmSeverity.MAJOR;

  

Help on this Alarm:   

When the Eyeglass Ransomware settings has monitor mode enable no lockout will occur. This alarm is a reminder that no data protection is enabled with monitor mode.

SCA0069


  RANSOMWARE_LEAVE_MONITOR_MODE(Code.SCA0069)


      description = "Ransomware: Left monitor only mode";
      severity = AlarmSeverity.MAJOR;

  
Help on this Alarm:   

When the Eyeglass Ransomware defender  setting disables monitor mode, this alarm indicates that data protection monitoring is now active.

SCA0070


  RANSOMWARE_ECA_VERSION(Code.SCA0070)


      description = "Ransomware: ECA node version does not match the Eyeglass version.";
      severity = AlarmSeverity.MAJOR;


  
Help on this Alarm:   

If the ECA cluster version does not match the Eyeglass version this alarm is raised.  The versions should match and upgrades should be completed to match ECA and Eyeglass versions.

SCA0071


  SECURITY_GUARD_FAILURE(Code.SCA0071) 


      description = "Ransomware: Security Guard Failure";
      severity = AlarmSeverity.MAJOR;


Help on this Alarm:   


The security if configured, runs on a schedule and failure should checked from the logs on the Ransomware defender icon, Security guard tab and open the last log to check which step failed.   This feature tests your defenses are active and functioning as expected.  This should be corrected and using service manager icon to verify the ECA is reachable and healthy.  Check the cluster igls-honey pot share exists.   Check other alarms in the alarms icon to verify the cluster(s) managed by the security guard feature can be reached.  Note SMB open port is required from Eyeglass to the Isilon clusters under management.