The NetApp LIF v2 sensor monitors a logical interface (LIF) of a NetApp storage system via the Representational State Transfer (REST) application programming interface (API) using ONTAP as of version 9.10.
This 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.
NetApp LIF v2 Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
Dutch: NetApp LIF v2
French: NetApp LIF v2
German: NetApp LIF v2
Japanese: NetApp LIF v2
Portuguese: LIF NetApp v2
Russian: LIF NetApp v2
Simplified Chinese: NetApp LIF v2
Spanish: LIF NetApp v2
Remarks
This sensor requires an ONTAP System Manager user account with specific access rights.
This sensor requires permissions for the ONTAP REST API.
This sensor requires ONTAP as of version 9.10. If you want to use NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to version 9.9, use the NetApp LIF sensor.
This sensor requires credentials for NetApp in settings that are higher in the object hierarchy.
This sensor supports IPv6.
This sensor has a very low performance impact.
This sensor uses lookups to determine the status values of one or more channels.
Detailed Requirements
Requirement
Description
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 sensorrequires the role readonly with the following permissions for the ONTAP REST API:
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
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:
lif
netapp
ontap
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 () to the highest priority ().
NetApp Specific
NetApp Specific
Setting
Description
Name
The name of the LIF that this sensor monitors.
Home Node Name
The home node name of the LIF that this sensor monitors.
Scope
The scope of the LIF that this sensor monitors.
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.
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.
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 name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file 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.
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 under the corresponding setting name to disable the inheritance and to display its options.
The minimum scanning interval of this sensor is 1 minute.
The recommended scanning interval of this sensor is 1 minute.
Scanning Interval
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You 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
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
Channel Unit Configuration
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel
Description
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