PRTG Manual: NetApp LIF Sensor
The NetApp LIF sensor monitors logical interfaces of a NetApp cDOT or ONTAP cluster accessing the application programming interface (API) via the Simple Object Access Protocol (SOAP).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: NetApp LIF
- French: NetApp LIF
- German: NetApp LIF
- Japanese: NetApp LIF
- Portuguese: LIF NetApp
- Russian: LIF NetApp
- Simplified Chinese: NetApp LIF
- Spanish: LIF NetApp
- This sensor requires Microsoft .NET 4.7.2 or later on the probe system.
- The ONTAPI user account that you use with this sensor needs access to the DATA ONTAP API (ONTAPI) so that the sensor can request data from it. The access is enabled by default.
- For this sensor, read-only user rights are sufficient for the ONTAPI user account that you use to access ONTAPI. Modify or add this user with a suitable role in the console under Cluster | ClusterX | Configuration | Security | Users
- This sensor supports NetApp cDOT as of version 8.3 and NetApp ONTAP as of version 9.0.
- This sensor supports the IPv6 protocol.
- This sensor has a very low performance impact.
- You can define NetApp API credentials (User Name and Password) in the credentials for Windows systems settings of the parent device. This way, you do not need to individually enter credentials for each NetApp sensor that you add to the same device.
- 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.
Requirement |
Description |
---|---|
.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 |
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.
PRTG performs a meta-scan before you can add this sensor and requires basic information in advance. Provide the required information in the dialog box that appears. PRTG then recognizes all items that are available for monitoring based on your input.
NetApp Connection
Setting |
Description |
---|---|
NetApp Credentials |
Specify which credentials you want to use to connect to the NetApp API:
|
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:
|
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. |
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
Setting |
Description |
---|---|
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. |
Click the Settings tab of a sensor to change its 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. 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:
|
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 (). |
Usually, 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.
Setting |
Description |
---|---|
NetApp Credentials |
Specify which credentials you want to use to connect to the NetApp API:
|
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:
|
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. |
NetApp Specific
Setting |
Description |
---|---|
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. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
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. |
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:
|
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. |
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.
For more information, see section Inheritance of Settings.
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.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
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
|
Packets Received |
The number of packets received per second |
Packets Sent |
The number of packets sent per second |
Knowledge Base
Which .NET version does PRTG require?
What security features does PRTG include?