<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: NetApp LIF Sensor

This sensor supports NetApp cDOT as of version 8.3 or ONTAP as of version 9.0. If you use ONTAP as of version 9.10, we recommend to use the NetApp LIF v2 sensor instead. The NetApp LIF v2 sensor is currently part of the Beta Sensors experimental feature of PRTG. For more information, see the Knowledge Base: What are beta sensors and how can I use them?

.NET 4.7.2 or later

This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

Enabled ONTAPI access

NetApp sensors require access to ONTAPI for the utilized user account. This is enabled by default. If access is disabled, locally use the following command on the cluster console to enable ONTAPI access for the user:

services web> modify -vserver clusterd -name ontapi -enabled true

NetApp Credentials

Specify which credentials you want to use to connect to the NetApp API:

• Use explicit credentials: Use individual NetApp API credentials.
• Use Windows credentials from parent device: Use the credentials (User Name and Password) in the parent device settings in section Credentials for Windows Systems.
  Defining credentials in the parent device is useful if you add several NetApp sensors to this device because you do not need to individually enter credentials for each NetApp sensor.

User Name

This setting is only visible if you select Use explicit credentials above. Enter a user name for access to the NetApp API. Enter a string.

Read-only rights for this ONTAP user account are sufficient.

Password

This setting is only visible if you select Use explicit credentials above. Enter the password of the user for access to the NetApp API. Enter a string.

Port

Enter a port number on which you can access the NetApp API. Enter an integer. The default port is 443.

Connection Security

Define if the connection to the NetApp API is Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured:

• HTTP: Use an unsecured HTTP connection.
• HTTPS: Use a secure connection to the defined port to send the query.

Timeout (Sec.)

Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes).

If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message.

Click OK to define the sensor settings.

LIFs

Select the LIFs that you want to monitor. PRTG creates one sensor for each LIF that you select.

Enable 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.

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.

This 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.

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

For 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
• cdot
• ontap
• soap

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 () to the highest priority ().

NetApp Credentials

Specify which credentials you want to use to connect to the NetApp API:

• Use explicit credentials: Use individual NetApp API credentials.
• Use Windows credentials from parent device: Use the credentials (User Name and Password) in the parent device settings in section Credentials for Windows Systems.
  Defining credentials in the parent device is useful if you add several NetApp sensors to this device because you do not need to individually enter credentials for each NetApp sensor.

User Name

This setting is only visible if you select Use explicit credentials above. Enter a user name for access to the NetApp API. Enter a string.

Read-only rights for this ONTAP user account are sufficient.

Password

This setting is only visible if you select Use explicit credentials above. Enter the password of the user for access to the NetApp API. Enter a string.

Port

Enter a port number on which you can access the NetApp API. Enter an integer. The default port is 443.

Connection Security

Define if the connection to the NetApp API is Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured:

• HTTP: Use an unsecured HTTP connection.
• HTTPS: Use a secure connection to the defined port to send the query.

Timeout (Sec.)

Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes).

If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message.

LIFs

Shows the ID of the LIF that this sensor monitors.

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

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].Data.txt and Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

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

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

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.

You can set a different primary channel later by clicking 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.
  You 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.

Data Received

The data received in bytes per second

This channel is the primary channel by default.

Data Sent

The data sent in bytes per second

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.

Errors Received

The number of errors received per second

Errors Sent

The number of errors sent per second

Is Home

If the logical interface (LIF) is on the home port

• Up status: Yes
• Down status: No

Packets Received

The number of packets received per second

Packets Sent

The number of packets sent per second