<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: NetApp Physical Disk v2 Sensor

The NetApp Physical Disk v2 sensor monitors physical disks of a NetApp storage system via the Representational State Transfer (REST) application programming interface (API) using ONTAP as of version 9.9.

i_round_redThis sensor was converted to a new framework so that it will continue to function after the changes of the ONTAP REST API. This sensor now requires permissions for the ONTAP REST API and credentials for NetApp in settings that are higher in the object hierarchy, for example, in the settings of the parent device.

i_betaThis sensor is in beta status. The operating methods and the available settings are still subject to change. Do not expect that all functions work properly, or that this sensor works as expected at all.

NetApp Physical Disk v2 Sensor

NetApp Physical Disk v2 Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: NetApp Physical Disk v2
  • French: NetApp Physical Disk v2
  • German: NetApp Physical Disk v2
  • Japanese: NetApp Physical Disk v2
  • Portuguese: NetApp Physical Disk v2
  • Russian: NetApp Physical Disk v2
  • Simplified Chinese: NetApp Physical Disk v2
  • Spanish: NetApp Physical Disk v2

Remarks

  • This sensor requires that the Beta Sensors experimental feature is enabled.
  • This sensor requires credentials for NetApp in settings that are higher in the object hierarchy, for example, in the settings of the parent device.
  • This sensor requires an ONTAP System Manager user account with specific access rights.
  • This sensor requires permissions for the ONTAP REST API.
  • This sensor supports ONTAP as of version 9.9. If you want to use NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to version 9.8, use the NetApp Physical Disk sensor instead.
  • This sensor requires ONTAP 9.10 for some channels.
  • This sensor supports the IPv6 protocol.
  • This sensor has a very low performance impact.
  • This sensor uses lookups to determine the status values of one or more channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.

Detailed Requirements

Requirement

Description

Enabled Beta Sensors experimental feature

This sensor requires that the Beta Sensors experimental feature of PRTG is enabled.

i_square_cyanFor more information, see the Knowledge Base: What are beta sensors and how can I use them?

Credentials for NetApp

This sensor requires an ONTAP System Manager user account with the role readonly and with access to the HTTP application with Password authentication.

Permissions for the ONTAP REST API

This sensor requires the role readonly with the following permissions for the ONTAP REST API:

Access level Read-Only:

  • /api
  • /api/security/audit/destinations

Access level Read/Write:

  • /api/security/authentication/password

Access level None:

  • /api/security

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.

NetApp Specific

i_round_blueThe settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.

Setting

Description

Disk

Select the physical disks that you want to monitor. PRTG creates one sensor for each physical disk that you select.

i_round_blueEnable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Basic Sensor Settings

Basic Sensor Settings

Setting

Description

Sensor Name

Enter a name to identify the sensor.

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

i_round_blueThis setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

i_round_blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

i_round_blueFor performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

  • netapp
  • ontap
  • physicaldisk
  • rest

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority (i_priority_1) to the highest priority (i_priority_5).

i_round_blueUsually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.

NetApp Specific

NetApp Specific

NetApp Specific

Setting

Description

Disk Name

Shows the name of the physical disk that this sensor monitors.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Home Node Name

Shows the home node name of the physical disk that this sensor monitors.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Sensor Display

Sensor Display

Sensor Display

Setting

Description

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    i_round_redYou cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Debug Options

Debug Options

Debug Options

Setting

Description

Result Handling

Define what PRTG does with the sensor result:

  • Discard result: Do not store the sensor result.
  • Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt, Result of Sensor [ID].Data.txt, and Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn a cluster, PRTG stores the result in the PRTG data directory of the master node.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

i_round_blueThe recommended scanning interval of this sensor is 1 minute.

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel

Description

Container Type

The type of the container

  • Up status: Aggregate, Foreign, Labelmaint, Maintenance, Shared, Spare, Unsupported, Remote, Mediator
  • Warning status: Unassigned, Unknown
  • Down status: Broken
  • Unknown status: Channel Value Not Set

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status in percent.

IOPS Total

The total number of IOPS

Latency

The latency in milliseconds (msec)

Path Error Count

The path error count

Power On Hours

The total time that the disk has been spinning

Throughput

The throughput per second

i_round_blueThis channel is the primary channel by default.

More

i_square_blueKNOWLEDGE BASE

What are beta sensors and how can I use them?

What security features does PRTG include?