PRTG Manual: Enterprise Virtual Array Sensor
The Enterprise Virtual Array sensor monitors an HPE Storage Enterprise Virtual Array (EVA) using the sssu.exe from HPE P6000 Command View Software (previously known as HP Command View EVA Software).
The sensor can show the status of several HPE EVA modules, depending on the available measurement components:
- System controllers
- Enclosures
- Disks
- Disk groups
- Folders
- Hosts
- Snapshots
- Data replication
- Cabinets
- If the devices have measuring tools for fans and temperature, the sensor displays corresponding data as well.
For these EVA components, this sensor can show the following:
- Operational status
- Predicted failures
- Accessible media
- Allocation in percent
- Availability for VRaids in bytes
- Exaggerated bytes
- Group host access
- Number of grouped and ungrouped disks
- Age of snapshots
- License status
Which channels the sensor actually shows might depend on the monitored device and the sensor setup.
- Dutch: Enterprise Virtual Array
- French: Enterprise Virtual Array
- German: Enterprise Virtual Array
- Japanese: Enterprise Virtual Array
- Portuguese: Enterprise Virtual Array
- Russian: Enterprise Virtual Array
- Simplified Chinese: Enterprise Virtual Array
- Spanish: Enterprise Virtual Array
- You must explicitly specify the credentials for the EVA in the sensor settings.
- This sensor requires the HPE P6000 Command View Software (previously known as HP Command View EVA Software) on the probe system, or the alternative described in the Knowledge Base: Do I really have to install the whole Command View on the probe to use the EVA sensor?
- This sensor supports the IPv6 protocol.
- This sensor has a high 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.
You cannot add this sensor to the hosted probe of a PRTG hosted by Paessler instance. If you want to use this sensor, add it to a remote probe device.
Requirement |
Description |
---|---|
HPE 6000 Command View Software |
This sensor needs the HPE P6000 Command View Software (previously known as HP Command View EVA Software) installed on the probe system.
|
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the setting fields that are required for creating the sensor. Therefore, you do not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.
PRTG performs a meta-scan before you can actually add this sensor and requires basic information for this scan in advance. Provide the requested information in the appearing dialog box. During the scan, PRTG recognizes all items available for monitoring based on your input. The following settings differ in comparison to the sensor's Settings tab.
Setting |
Description |
---|---|
Scanning Mode |
Specify the depth of the meta-scan:
|
Select the modules that you want to monitor. PRTG creates one sensor for each module that you select. The settings you select are valid for all sensors that you create when you finish this dialog.
The following settings in the Add Sensor dialog differ in comparison to the sensor's Settings tab.
Setting |
Description |
---|---|
Modules |
Select the modules that you want to add a sensor for. You see a list with the names of all items that you can monitor. Add check marks in front of the respective lines to select the desired items. You can also use the check box in the table header to select all items or cancel the selection.
|
Click the Settings tab of a sensor to change its settings.
Usually, a sensor connects to the IP Address or DNS Name of the parent device on which you created the sensor. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings. See below for details on available settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a meaningful name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
Shows tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is shown for your information only and cannot be changed here. |
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.
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 ( |
EVA Credentials
Setting |
Description |
---|---|
Username |
Enter the username for the EVA. |
Password |
Enter the password for the EVA. |
EVA Settings
Setting |
Description |
---|---|
Module |
Shows the monitored module. You can adjust this setting if the module was renamed or moved to a different folder. This way, PRTG can find the module again and the monitoring history is not lost. |
System |
Shows further information about the monitored module. Once you have created the sensor, you cannot change this value. It is shown for reference purposes only. If you need to change this value, add the sensor anew. |
Module Type |
|
Description |
|
Result Handling |
Define what PRTG does with the sensor result:
|
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.
|
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 the following settings are inherited from objects that are higher in the hierarchy. You should 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. You then see the options described below.
For more information, see section Inheritance of Settings.
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Scanning Interval |
Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:
|
If a Sensor Query Fails |
Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:
|
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.
Setting |
Description |
---|---|
Schedule |
Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:
|
Maintenance Window |
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
|
Maintenance Begins |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window. |
Maintenance Ends |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window. |
Dependency Type |
Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
Dependency Delay (Sec.) |
This setting is only visible if you enable Select a sensor above. Define a time span in seconds for the dependency delay. After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
User Group Access |
Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Channel Unit Types |
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, these settings can be inherited to all sensors underneath. You can set units for the following channel types (if available):
|
KNOWLEDGE BASE
Do I really have to install the whole Command View on the probe to use the EVA sensor?
For more information about sensor settings, see the following sections: