Skip to main content

EMC Symmetrix CMA

Connector dependencies​

The following monitoring connectors will be installed when you install the EMC Symmetrix CMA connector through the Configuration > Connectors > Monitoring Connectors menu:

Pack assets​

Templates​

The Monitoring Connector EMC Symmetrix CMA brings 2 host templates:

  • HW-Storage-EMC-Symmetrix-Dmx34-CMA-custom
  • HW-Storage-EMC-Symmetrix-Vmax-CMA-custom

The connector brings the following service templates (sorted by the host template they are attached to):

Service AliasService TemplateService Description
Hardware-GlobalHW-Storage-EMC-Symmetrix-Dmx34-Hardware-Global-CMA-customCheck hardware components state

The services listed above are created automatically when the HW-Storage-EMC-Symmetrix-Dmx34-CMA-custom host template is used.

Collected metrics & status​

Here is the list of services for this connector, detailing all metrics and statuses linked to each service.

NameUnit
director.statusN/A
xcm.statusN/A
disk.statusN/A
memory.statusN/A
test.statusN/A
fru.statusN/A
module.statusN/A
temperature.statusN/A
cabling.statusN/A
power.statusN/A
fabric.statusN/A
voltage.statusN/A
spreadisk.statusN/A

Prerequisites​

Network flow​

Only one TCP flow must be open from the host to the poller.

SourceDestinationProtocolPortPurpose
Monitored hostCollecteurTCP4317Configuration retrieval, and OpenTelemetry data flow

System prerequisites on the poller​

To be able to use the Centreon Monitoring agent, you must use a poller with at least version 24.10 for On Prem users of centreon-engine. The Centreon Monitoring agent will configure itself by connecting to Centreon Engine.

Configure Engine​

Configure how the poller and the agent will communicate. (This link directs you to the latest version of the OnPrem documentation. Use the version selector in the top right corner to switch to another version if you need to.)

System prerequisites on the monitored host​

The installer can be downloaded from the centreon-collect's releases page.

Installing the Centreon Monitoring Agent​

The installation and configuration procedure of the Centreon Monitoring Agent is detailed in this dedicated page. This includes installing the agent, and installing the plugins that will execute the non-native checks. (This link directs you to the latest version of the OnPrem documentation. Use the version selector in the top right corner to switch to another version if you need to.)

Installing the monitoring connector​

Pack​

The installation procedures for monitoring connectors are slightly different depending on whether your license is offline or online.

  1. If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Connectors > Monitoring Connectors menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
dnf install centreon-pack-hardware-storage-emc-symmetrix-cma
  1. Whatever the license type (online or offline), install the EMC Symmetrix CMA connector through the Configuration > Connectors > Monitoring Connectors menu.

Plugin​

This connector relies on an integration supported by Centreon Engine and does not need a plugin.

Using the monitoring connector​

Using a host template provided by the connector​

  1. Log into Centreon and add a new host through Configuration > Hosts.
  2. Fill in the Name, Alias & IP Address/DNS fields according to your resource's settings.
  3. Apply the HW-Storage-EMC-Symmetrix-Dmx34-CMA-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
  4. Fill in the macros you want. Some macros are mandatory.
MacroDescriptionDefault valueMandatory
CENTREONAGENTPLUGINSPath where the centreon_plugins.exe plugin can be foundC:/Program Files/Centreon/PluginsX
SYSTEMLANGUAGELanguage installed on the Windows systemen
  1. Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.

Using a service template provided by the connector​

  1. If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
  2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).
MacroDescriptionDefault valueMandatory
COMPONENTWhich component to check (default: '.*'). Can be: 'module', 'temperature', 'director, 'cabling', 'power', 'voltage', 'sparedisk'.*
FILEHEALTHName of the global storage file status (default: HealthCheck.log)
FILEHEALTHENVName of the environment storage file status (default: sympl_env_health.log)
EXTRAOPTIONSAny extra option you may want to add to the command (a --verbose flag for example). All options are listed here.--verbose
  1. Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.

How to check in the CLI that the configuration is OK and what are the main options for?​

Once the plugin is installed, log into your Centreon poller's CLI using the centreon-engine user account (su - centreon-engine). Test that the connector is able to monitor a resource using a command like this one (replace the sample values by yours):

C:/Program Files/Centreon/Plugins/centreon_plugins.exe" \
    --plugin=storage::emc::symmetrix::vmax::local::plugin \
    --mode=hardware \
	--file-health-name="" \
	--file-health-env-name="" \
	--component=".*" \
	--verbose'

The expected command output is shown below:

OK: All 2 components are ok [2/2 temperatures]. | 'temp1 Temp'=30C;;;;'temp2 Temp'=31C;;;;'count_temperature'=2;;;;

Troubleshooting​

Please find the troubleshooting documentation for Centreon Plugins typical issues.

Available modes​

In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. However, you will need to specify the correct mode for the template if you want to test the execution command for the connector in your terminal.

All available modes can be displayed by adding the --list-mode parameter to the command:

C:/Program Files/Centreon/Plugins/centreon_plugins.exe" \
    --plugin=storage::emc::symmetrix::vmax::local::plugin \
	--list-mode

The plugin brings the following modes:

ModeLinked service template
hardware [code]HW-Storage-EMC-Symmetrix-Dmx34-Hardware-Global-CMA-custom
HW-Storage-EMC-Symmetrix-Vmax-Hardware-Global-CMA-custom

Available options​

Modes options​

All available options for each service template are listed below:

OptionDescription
--componentWhich component to check (default: '.*'). Can be: 'module', 'temperature', 'director, 'cabling', 'power', 'voltage', 'sparedisk'.
--filterExclude the items given as a comma-separated list (example: --filter=temperature --filter=module). You can also exclude items from specific instances: --filter=temperature,ES-PWS-A ES-4
--absent-problemReturn an error if a component is not 'present' (default is skipping). It can be set globally or for a specific instance: --absent-problem='component_name' or --absent-problem='component_name,instance_value'.
--no-componentDefine the expected status if no components are found (default: critical).
--threshold-overloadUse this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,[instance,]status,regexp). Example: --threshold-overload='director,WARNING,^(?!(OK)$)'
--warningSet warning threshold for disk (syntax: type,regexp,threshold) Example: --warning='sparedisk,.*,5:'
--criticalSet critical threshold for disk (syntax: type,regexp,threshold) Example: --critical='sparedisk,.*,3:'
--warning-count-*Define the warning threshold for the number of components of one type (replace '*' with the component type).
--critical-count-*Define the critical threshold for the number of components of one type (replace '*' with the component type).
--memcachedMemcached server to use (only one server).
--redis-serverRedis server to use (only one server). Syntax: address[:port]
--redis-attributeSet Redis Options (--redis-attribute="cnx_timeout=5").
--redis-dbSet Redis database index.
--failback-fileFall back on a local file if Redis connection fails.
--memexpirationTime to keep data in seconds (default: 86400).
--statefile-dirDefine the cache directory (default: '/var/lib/centreon/centplugins').
--statefile-suffixDefine a suffix to customize the statefile name (default: '').
--statefile-concat-cwdIf used with the '--statefile-dir' option, the latter's value will be used as a sub-directory of the current working directory. Useful on Windows when the plugin is compiled, as the file system and permissions are different from Linux.
--statefile-formatDefine the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default).
--statefile-keyDefine the key to encrypt/decrypt the cache.
--statefile-cipherDefine the cipher algorithm to encrypt the cache (default: 'AES').
--health-directoryLocation of health files.
--health-directory-patternSet pattern to match the most recent directory (getting the hexa value).
--file-health-nameName of the global storage file status (default: HealthCheck.log).
--file-health-env-nameName of the environment storage file status (default: sympl_env_health.log).

All available options for a given mode can be displayed by adding the --help parameter to the command:

C:/Program Files/Centreon/Plugins/centreon_plugins.exe" \
    --plugin=storage::emc::symmetrix::vmax::local::plugin \
    --mode=hardware \
	--help