SU513: [Impact: High] ONTAP Tools for VMware vSphere (OTV) 9.8 can cause high CPU usage

Views:
546
Last Updated:
9/24/2022, 12:16:04 AM

收藏

Summary

[Impact High: High CPU causing short term loss of data access]

If OTV is configured so that the source ONTAP cluster is peered to more than 1 other ONTAP cluster, a defect in OTV can cause very high CPU usage in the ONTAP HostOS domain when the Storage Replication Adaptor (SRA) rediscovery is triggered. The SRA rediscovery is normally triggered every 75 minutes.

This issue exists in the OTV Release 9.8 and 9.10 (There is no OTV 9.9)

Issue Description

If OTV is configured with the source ONTAP cluster peered to more than 1 other ONTAP cluster, SRA can cause very high CPU usage in the ONTAP HostOS domain during rediscovery. If the source cluster is peered to only 1 other cluster, this does not occur. The issue is due to a defect introduced in OTV 9.8 and fixed in OTV 9.11. This is BUG 1482110.

Symptom

High CPU usage in the HostOS domain resulting is possible performance degradation.

Workaround

The preferred solution is to upgrade OTV to OTV release 9.11.

The workaround is to disable the VP (VASA Provider) discovery. In this case the VP is the ONTAP system connected to OTV.

Disable VP periodic rediscovery
  1. Log into VP Control Panel (https://OTV:9083)
  2. Run the following from WebCLI:
    1. vp updateconfig -key=discovery.periodic.inventory.flexvols.sleep.time -value=0
    2. vp updateconfig -key=discovery.periodic.inventory.sleep.time -value=0
    3. vp reloadconfig
  3. Disable VP:
    1. Toggle setting via OTV UI: ONTAP Tools > Settings > Manage Capabilities
Disable the workaround after upgrade to OTV 9.11
  1. Enable VP periodic rediscovery:
    1. Log into VP Control Panel (https://OTV:9083)
    2. Run the following from WebCLI:
      1. vp updateconfig -key=discovery.periodic.inventory.flexvols.sleep.time -value=30
      2. vp updateconfig -key=discovery.periodic.inventory.sleep.time -value=75
      3. vp reloadconfig
  2. Enable VP:
    1. Toggle setting via OTV UI: ONTAP Tools > Settings > Manage Capabilities

Contact NetApp Support for questions and/or assistance.

Solution

Upgrade to OTV 9.11 which has the fix for BUG 1482110.