跳转到主内容

AIQUM中的SnapMirror滞后阈值不正确

Views:
38
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

适用场景

  • ActiveIQ Unified Manager (AIQUM) 9.6及更高版本
  • ONTAP 9
  • SnapMirror

问题描述

  • AIQUM每X 小时报告一次Mirror Replication Lag Warning 警报
  • 实际SnapMirror关系对计划使用的值大于警告值
    • 例如:
      • AIQUM中的滞后警告每2小时发出一次
      • 滞后警告阈值设置为150%
      • 在SnapMirrr中、此计划设置为2小时间隔
      • 因此、150%应为3小时 
  • AIQUM未正确计算SnapMirror关系的警告和错误阈值
  • AIQUM au.log 显示: 
    WARN  [foundation-poll-2] c.o.s.a.d.n.t.z.ZAPIConnection (ZAPIConnection.java:729) - [netappfoundation] <cluster_fqdn> - <cluster_fqdn> <cluster_fqdn> - Ignoring failed zapi: job-schedule-cron-get-iter; errno: 13115, reason: Invalid value specified for "key-0" element within "job-schedule-cron-get-iter-key-td":"<stale_cluster_uuid>"
  • 在ONTAP中运行作业计划show时、会显示一些计划、其中集群名称为陈旧UUID、而不是正确的集群名称
    > job schedule show  -fields cluster,description
    cluster                vserver   name        description
    ------------------------------------ --------- ----------------- ------------
    <stale_cluster_uuid>         <vserver> <schedule>     <schedule_description>
    <stale_cluster_uuid>         <vserver><schedule>     <schedule_description>
  • 在System Manager中、单击 "保护">"概述">"本地策略设置">"计划"
    • 某些计划的计划为空
    • 尝试编辑这些计划时、它只会永久加载到图形用户界面中、而不会加载任何内容

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.