Skip to main content
Keystone

Configure AutoSupport for Keystone

Contributors netapp-manini
PDFs

When using the AutoSupport telemetry mechanism, Keystone calculates the usage based on the AutoSupport telemetry data. To achieve the necessary level of granularity, you should configure AutoSupport to incorporate Keystone data in the daily support bundles sent by the ONTAP clusters.

About this task

You should note the following before configuring AutoSupport to include Keystone data.

  • You edit the AutoSupport telemetry options by using ONTAP CLI. For information about managing AutoSupport services and system (cluster) administrator role, see Manage AutoSupport overview and Cluster and SVM administrators.

  • You include the following subsystems in the daily AutoSupport bundles to ensure precise data collection for Keystone. For information about AutoSupport subsystems, see What AutoSupport subsystems are.

    Subsystem name Data item required for Keystone

    wafl

    VOLUME-CLONE-SHOW.XML

    performance

    QOS-POLICY-GROUP.XML and QOS-ADAPTIVE-POLICY.XML

    snapshot

    SNAPSHOT.XML

    platform

    ENVIRONMENT.txt

    These subsystems are included by default in the weekly AutoSupport bundles, where the asup_type is DOT-REGULAR, and the asup_subject is HA Group Notification (WEEKLY_LOG) NOTICE. However, you need to add them to daily bundles for retrieving and reporting Keystone usage data.

Steps

  1. As a system administrator user, log in to the Keystone ONTAP cluster by using SSH. For information, see Access the cluster by using SSH.

  2. Run the following command and verify the existing configuration with respect to the existing subsystems:

    autosupport trigger show -node * -autosupport-message management.log -fields basic-additional

    For more information about this command, see system node autosupport manifest show.

  3. Modify the daily log content by running this command:

    autosupport trigger modify -node * -autosupport-message management.log -basic-additional <existing comma-separated subsystems>, <new subsystems>

    For more information about this command, see system node autosupport trigger modify.