Skip to main content
NetApp Knowledge Base

High Latency with SM-BC caused by network issues

  1. Last updated
    May 22, 2025
  2. Save as PDF
Views:
284
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
Perf
Last Updated:
5/22/2025, 8:30:13 AM

Applies to

  • ONTAP 9
  • SnapMirror Active Sync (SM-AS)/SnapMirror Business Continuity (SM-BC)

Issue

  • High latency reported from SnapMirror Sync
    • SM-AS/SM-BC relies on SnapMirror Sync (SM-S)
    • CLI command qos statistics workload latency show shows the high latency from SM Sync
    • AIQUM/OCUM shows the high latency from Sync SnapMirror
  • EMS errors are logged on the primary site:

Tue Apr 04 02:38:22 +0800 [Node1-01: repl_Handle_sync_resl: callhome.syncsm.exception:error]: Call home for SNAPMIRROR SYNCHRONOUS EXCEPTION: Network Latency exceeded threshold limit.

  • CLI command network test-link shows a high network latency between the source and destination cluster
 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.