The Enterprise Virtual Array sensor monitors an HPE Storage Enterprise Virtual Array (EVA) via the sssu.exe from HPE P6000 Command View Software (previously known as HP Command View EVA Software).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
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
Remarks
This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
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:
eva
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 ().
EVA Credentials
Setting
Description
User Name
Enter the user name for the EVA.
Password
Enter the password for the EVA.
EVA Settings
Setting
Description
Module
The module that this sensor monitors.
You can edit this setting if, for example, you rename the module or move it to a different folder. This way, PRTG can find the module again and you do not lose the monitoring history.
System
The system of the module that this sensor monitors.
Module Type
The type of the module that this sensor monitors.
Description
The description of the module that this sensor monitors.
Result Handling
Define what PRTG does with the sensor result:
Discard result (default): 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 and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.
In a cluster, PRTG stores the result in the PRTG data directory of the master node.
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 select Stack channels on top of each other above.
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.
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.
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 (default).
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
Channel Unit Configuration
For more information, see section Root Group Settings, section Channel Unit Configuration.
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
This sensor can show the status of several HPE EVA modules:
System controllers
Enclosures
Disks
Disk groups
Folders
Hosts
Snapshots
Data replication
Cabinets
If the devices have measuring tools for fans and temperature, this 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
More
KNOWLEDGE BASE
Do I really have to install the whole Command View on the probe to use the EVA sensor?