Map Your Own IT Ecosystem
See how Zenoss fits into your IT ecosystem.
Start MAPPING NOW
Huntington Success Story
Learn how Huntington consolidated from 37 tools to a single monitoring solution.
Customer Support Portal
Zenoss Learning Center
Zenoss & Cisco: Changing IT with service assurance for hybrid data centers.
Zenoss Partner Portal
Become a Partner
BBC Success Story
The BBC chose Zenoss for three key reasons: scalability, flexibility and value for money.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
For monitoring block storage, the EMC base ZenPack enables Resource Manager to use the Web Based Enterprise Management (WBEM) protocol to monitor and model VNX and VMAX devices under /Storage/EMC/VNX and /Storage/EMC/VMAX device classes by executing queries and parsing the output. Parsing of this information is performed on the Resource Manager server (if using a local collector) or on a distributed collector. Information is gathered via the EMC Storage Management Initiative Specification (SMI-S) Provider.
The following video demonstrates how to setup block storage monitoring via SMI-S on EMC.base versions 1.0.5 and 1.1.2.
The following components will be discovered when modeled.
The following datapoints will be collected every 5 minutes by default.
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for EMC devices. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities.
For monitoring file storage, the EMC base ZenPack enables Resource Manager to communicate with the VNX XML API Server under /Storage/EMC/VNXFile device class. The API queries are made directly to the VNX Control Station from the Resource Manager server (if using a local collector) or on a distributed collector. If the XML API Server is disabled, instructions on Starting the XML API Server are detailed below in this page.
Reference: EMC API documents available here: https://community.emc.com/docs/DOC-19626
Graphs populate when collector collects File System and Storage Pool metrics
The following datapoints are collected every 5 minutes by default.
Zenoss periodically polls the Control Station for VNX events and creates Zenoss events when they occur. Events can be configured either through the VNX device or blocked/filtered through the unique eventClassKey: emc-vnx-file-events| in Zenoss Resource Manager. Events are collected every 5 minutes by default.
EMC VNX File (Celerra) events are mapped to Zenoss events in the following way:
DART (Data Access in Real Time)
CS_CORE, XML_API, CS_PLATFORM
Reference: Mapping of Celerra message codes and Celerra descriptions are referenced from EMC's Configuring Celerra Events and Notifications
When combined with Zenoss Service Dynamics, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on VNX. The service impact relationships shown in the diagram and described below are automatically added and maintained. These will be included in any services that contain one or more of the discovered components listed above.
This ZenPack provides additional support for Zenoss Analytics. Perform the following steps to install extra reporting resources into Zenoss Analytics after installing the ZenPack.
You can now navigate back to the EMC base ZenPack folder in the repository to see the following resources added by the bundle.
Domains can be used to create ad hoc views using the following steps.
Installing this ZenPack will add the following items to your Zenoss system.
To monitor a VNX or VMAX storage device, select the Add EMC Storage option.
This will present an Add EMC Device - Block or File window.
Alternatively you can use zenbatchload to add VNX/VMAX block storage from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple endpoints can be added under the same /Devices/Storage/EMC/VNX or /Devices/Storage/EMC/VMAX section.
# For VNX (Block Storage) Devices
vnx_block setManageIp='<smi-s_address>', zCommandUsername='<smi-s_username>', zCommandPassword='<smi-s_password>'
# For VMAX (Block Storage) Devices
vmax_block setManageIp='<smi-s_address>', zCommandUsername='<smi-s_username>', zCommandPassword='<smi-s_password>'
You can then load the endpoint(s) with the following command.
To validate that data is being gathered correctly and that the SMI-S provider is configured correctly you can make direct calls via WBEM command line tools. On Linux you can install several tools via the local package manager to make these types of calls. One such tool is called wbemcli and below is a sample command you can execute to test data retrieval. Zenoss recommends that you **DO NOT** install this on the Zenoss server but onto a separate Linux installation that has a network path to the SMI-S provider.
wbemcli -dx -noverify ei 'http://:@:5988/root/emc:EMC_VolumeView'
wbemcli -dx -noverify ei '
This command will enumerate instances (ei) of the Disk Drive class. Please note, command format depends on installed version of the wbemcli tool. Please check usage documentation.
Alternatively you can use zenbatchload to add VNX file storage from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple endpoints can be added under the same /Devices/Storage/EMC/VNXFile.
# For VNX (File Storage) Devices
vnx_file setManageIp='<control_station_address>', zCommandUsername='<api_username>', zCommandPassword='<api_password>'
The following section is referenced from EMC API documents available from here: https://community.emc.com/docs/DOC-19626
From EMC® VNX™ for File 7.1 - XML API Programmers Guide (Pg. 180):
To start the XML API server, do the following:
As root, use a text editor to uncomment the following entry in /nas/sys/nas_mcd.cfg:
daemon “XML API Server”- executable “/nas/sbin/start_xml_api_server” optional yes canexit yes autorestart yes ioaccess no
Restart nas services with the following command:
# service nas start
The XML API is now started and is controlled by the master control daemon.
$ sudo su - zenoss
$ zenpack --install ZenPacks.zenoss.EMC.base-*.egg
$ zenoss restart
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.