Skip to main content
VCP

Monitor event logs for troubleshooting

Contributors netapp-pcarriga netapp-dbagwell amgrissino
PDFs

You can review event logs for operations performed on the selected cluster along with cluster faults that might occur. Most errors are resolved automatically by the system. Other faults might require manual intervention.

Steps

  1. From the vCenter Plug-in, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

  2. Select Reporting > Event Log.

  3. To review details, select an event and click Details.

  4. Review the event information that includes the following:

    • Event Type: The type of event being logged; for example, API events or clone events.

    • Service ID: The ID of the service that reported the event (if applicable). The value is zero if the fault is not associated with a service.

    • Node or Drive ID: The ID of the node or drive that reported the event (if applicable).

Event types

The system reports multiple types of events; each event is an operation that the system has completed. Events can be routine, normal events or events that require administrator attention. The Event Type column on the Event Log page indicates in which part of the system the event occurred.

Note The system does not log read-only API commands in the event log.

The following list describes the types of events that might appear in the event log.

  • apiEvent: Events initiated by a user through an API or web UI that modify settings.

  • binAssignmentsEvent: Events related to the assignment of data bins. Bins are essentially containers that hold data and are mapped across the cluster.

  • binSyncEvent: System events related to a reassignment of data among block services.

  • bsCheckEvent: System events related to block service checks.

  • bsKillEvent: System events related to block service terminations.

  • bulkOpEvent: Events related to operations performed on an entire volume, such as a backup, restore, snapshot, or clone.

  • cloneEvent: Events related to volume cloning.

  • clusterMasterEvent: Events appearing upon cluster initialization or upon configuration changes to the cluster, such as adding or removing nodes.

  • csumEvent: Events related to invalid data checksums on the disk.

  • dataEvent: Events related to reading and writing data.

  • dbEvent: Events related to the global database maintained by ensemble nodes in the cluster.

  • driveEvent: Events related to drive operations.

  • encryptionAtRestEvent: Events related to the process of encryption on a cluster.

  • ensembleEvent: Events related to increasing or decreasing the number of nodes in an ensemble.

  • fibreChannelEvent: Events related to the configuration of and connections to the nodes.

  • gcEvent: Events related to processes run every 60 minutes to reclaim storage on block drives. This process is also known as garbage collection.

  • ieEvent: Internal system error.

  • installEvent: Automatic software installation events. Software is being automatically installed on a pending node.

  • iSCSIEvent: Events related to iSCSI issues in the system.

  • limitEvent: Events related to the number of volumes or virtual volumes in an account or in the cluster nearing the maximum allowed.

  • maintenanceModeEvent: Events related to the node maintenance mode, such as disabling the node.

  • networkEvent: Events related to the status of virtual networking.

  • platformHardwareEvent: Events related to issues detected on hardware devices.

  • remoteClusterEvent: Events related to remote cluster pairing.

  • schedulerEvent: Events related to scheduled snapshots.

  • serviceEvent: Events related to system service status.

  • sliceEvent: Events related to the Slice Server, such as removing a metadata drive or volume.

    There are three types of slice reassignment events, which include information about the service where a volume is assigned:

  • flipping: changing the primary service to a new primary service

    sliceID oldPrimaryServiceID→newPrimaryServiceID

  • moving: changing the secondary service to a new secondary service

    sliceID {oldSecondaryServiceID(s)}→{newSecondaryServiceID(s)}

  • pruning: removing a volume from a set of services

    sliceID {oldSecondaryServiceID(s)}

  • snmpTrapEvent: Events related to SNMP traps.

  • statEvent: Events related to system statistics.

  • tsEvent: Events related to the system transport service.

  • unexpectedException: Events related to unexpected system exceptions.

  • ureEvent: Events related to Unrecoverable Read Errors that occur while reading from the storage device.

  • vasaProviderEvent: Events related to a VASA (vSphere APIs for Storage Awareness) Provider.

Find more information