Skip to main content
NetApp Knowledge Base

What kind of event will be detected when snapmirror failed?

  1. Last updated
  2. Save as PDF
Views:
84
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • SnapMirror
  • ONTAP 9

Answer

  • The event can be checked from the below command:

cluster1::> event catalog show -message-name snapmirror*
Message                          Severity         SNMP Trap Type
-------------------------------- ---------------- -----------------
snapmirror.block.on.reconstruct  NOTICE           Severity-based
snapmirror.block.reconstructErr  ERROR            Severity-based
snapmirror.conf.depre.cpsync     ERROR            Severity-based
snapmirror.conf.full             ERROR            Severity-based
snapmirror.conf.invalidStr       ERROR            Severity-based
snapmirror.conf.obsolete.nvsync  ERROR            Severity-based
snapmirror.copy.FailedErr        ERROR            Severity-based
......

cluster1::> event catalog show -message-name smc.snapmir*
Message                          Severity         SNMP Trap Type
-------------------------------- ---------------- -----------------
smc.snapmir.dst.invalidType      ERROR            Severity-based
smc.snapmir.frest.clean.fail     ERROR            Severity-based
smc.snapmir.init.fail            ERROR            Severity-based
smc.snapmir.lrb.auto.resync      INFORMATIONAL    Severity-based
smc.snapmir.partnr.noconnect     ERROR            Severity-based
smc.snapmir.release.fail         ERROR            Severity-based
......

  • For more details of the specific event, use the below command:

::> event catalog show -message-name smc.snapmir.update.fail
Message Name: smc.snapmir.update.fail
Severity: ERROR
Description: This message occurs when a scheduled SnapMirror(R) transfer fails.
Corrective Action: Check the snapmirror_error log in the destination filer and take action accordingly.
SNMP Trap Type: Severity-based
Is Deprecated: false

Additional Information

  • The event can be configured to send mail notification: How to configure event filter and event notification for email destination
  • Use the below method to trigger an event intentionally:
    • Pause the snapmirror by snapmirror quiesce 
      • smc.snapmir.update.fail: Snapmirror update from source volume 'cluster1_svm1:cluster1_svm1_inventory' to destination volume 'cluster2_svm1:cluster1_svm1_inventory_dest' failed with error 'Transfer did not start. The relationship is quiesced, or Vserver peering between source and destination Vservers has been suspended or removed.'. Relationship UUID 'c579a9d2-9d9e-11ef-a659-0050569cb19e'
    • Break the snapmirror by snapmirror break
      • smc.snapmir.update.fail: Snapmirror update from source volume 'cluster1_svm1:cluster1_svm1_inventory' to destination volume 'cluster2_svm1:cluster1_svm1_inventory_dest' failed with error 'Destination cluster2_svm1:cluster1_svm1_inventory_dest must be a data-protection volume.'. Relationship UUID 'c579a9d2-9d9e-11ef-a659-0050569cb19e'
    • Down the intercluster LIF by network interface modify -vserver cluster1 -lif inter_lif -status-admin down
      • smc.snapmir.schd.trans.overrun: Scheduled transfer from source volume 'cluster1_svm1:cluster1_svm1_inventory' to destination volume 'cluster2_svm1:cluster1_svm1_inventory_dest' is taking longer than the schedule window. Relationship UUID 'c579a9d2-9d9e-11ef-a659-0050569cb19e'​​​​​​​
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.