Домой

<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Enterprise Virtual Array Sensor

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

i_square_cyanFor 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.
  • This sensor supports IPv6.
  • This sensor uses lookups to determine the status values of one or more channels.

i_podYou cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.

Detailed Requirements

Requirement

Description

HPE P6000 Command View Software

This sensor requires the HPE P6000 Command View Software (previously known as HP Command View EVA Software) to be installed on the probe system.

i_square_cyanIf you do not want to install the whole command view tool, you can use a different option. For more information, see the Knowledge Base: Do I really have to install the whole Command View on the probe to use the EVA sensor?

Add Sensor

Setting

Description

Scanning Mode

Specify the depth of the meta-scan:

  • Basic mode: We recommend that you use this scanning mode. Various modules of your EVA are available for monitoring.
  • Detailed mode: PRTG scans for each disk of your EVA. It lists every disk in the module selection.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

Setting

Description

Sensor Name

Enter a 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.

i_round_blueIf 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?

Parent Tags

The tags that the sensor inherits from its parent device, parent group, and parent probe.

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

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

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

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.

i_round_blueYou 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: 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.

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

Sensor Display

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.

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

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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou 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

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

i_round_blueWhich 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

Channel Unit Configuration

i_square_cyanFor more information, see section Root Group Settings, section Channel Unit Configuration.

Channel List

i_round_blueWhich 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

i_square_blueKNOWLEDGE BASE

Do I really have to install the whole Command View on the probe to use the EVA sensor?

What security features does PRTG include?