Splunk® Supported Add-ons

Splunk Add-on for EMC VNX

Download manual as PDF

Download topic as PDF

Release history for the Splunk Add-on for EMC VNX

Latest release

The latest version of the Splunk Add-on for EMC VNX is version 1.2.0. Please see the previous topic for release notes of this latest version.

Version 1.1.1

Version 1.1.1 of the Splunk Add-on for EMC VNX is compatible with:

Splunk platform versions 6.3 and above
CIM 3.0 and above
Platforms Platform independent
Vendor Products EMC VNX, VNX2 series

New features

Version 1.1.1 of the Splunk Add-on for EMC VNX does not add any new features.

Fixed issues

Version 1.1.1 of the Splunk Add-on for EMC VNX fixes the following issues:

Resolved date Defect number Description
10/13/16 EMCVNX-32 The user needs to re-enter username/password for the add-on every time Splunk is restarted
10/13/16 EMCVNX-25 Encrypted password breaks data collection
09/26/16 EMCVNX-106 EMC VNX: App Inspect issues
09/26/16 EMCVNX-35 Data collection breaks after Splunk restart
09/26/16 EMCVNX-9 Names of event types include colons
09/26/16 EMCVNX-29 Configuration files do not follow best practices
09/26/16 EMCVNX-17 Pre-built panel titles do not adhere to Splunk naming conventions
09/26/16 EMCVNX-1 Missing the following line in the UI part of app.conf: docs_section_override\\s*=\\s*AddOns:released
09/26/16 EMCVNX-31 Event types are not URI encoded

Known issues

Version 1.1.1 of the Splunk Add-on for EMC VNX has the following known issues:

Publication date Defect number Description
09/30/16 EMCVNX-161 Error: "No data collection for VNX is found in the inputs.conf"
05/19/16 EMCVNX-63 Cannot configure the authentication scope with Splunk Add-on for EMC VNX

Third-party software attributions

Version 1.1.1 of the Splunk Add-on for EMC VNX does not incorporate any third-party software or libraries.

Version 1.1.0

Version 1.1.0 of the Splunk Add-on for EMC VNX is compatible with:

Splunk platform versions 6.1 and above
CIM 3.0 and above
Platforms Platform independent
Vendor Products EMC VNX series

Migration

Note: If your current version is 1.0.1 and you want to upgrade to 1.1.0, this section does not apply to you. You can update from 1.0.1 by checking for upgrades within Splunk Web or using the CLI.

If you have version 1.0.0 of the Splunk Add-on for EMC VNX currently installed and have not upgraded to version 1.0.1, note that version 1.1.0 will not update or replace your current installation. Because the file name and folder structure were updated in version 1.0.1 to match standard naming structure, the add-on behaves as a new installation, not an upgrade.

As of version 1.0.1, the folder name, sourcetype names, and default index behavior have changed. Review your local app.conf, props.conf, and indexes.conf and make any appropriate changes.

To migrate from version 1.0.0 to 1.1.0:

  1. Download and install version 1.1.0 of the add-on
  2. Disable version 1.0.0 in Splunk Enterprise
  3. Enable version 1.1.0 of the add-on
  4. Create and adjust your local conf files as needed to match your old configurations
  5. Verify your configurations work as expected
  6. Delete version 1.0.0 of the add-on

New features

Version 1.1.0 of the Splunk Add-on for EMC VNX adds the following new features:

Resolved date Ticket number Description
10/27/14 ADDON-1645 Modular panels added.
10/21/14 ADDON-2024 The add-on now calculates the fields avg_busy_queue_length, avg_busy_queue_width, response_time, and service_time of the VNX Storage Processor in props.conf.
10/14/14 ADDON-2114 New field extractions to match additional CIM fields cpu_count, cpu_load_percent, dest, mem, read_blocks, storage_free, storage_used, storage_used_percent, vendor, write_blocks

Fixed issues

Version 1.1.0 of the Splunk Add-on for EMC VNX fixes the following issues:

Resolved date Defect number Description
11/03/14 ADDON-2229 Sourcetypes docx file should be removed from package
10/14/14 ADDON-2060 Mistake in mapping "storage_used_percent" in the props.conf for "vnx:file:diskVolumePerf" source type.

Known issues

Version 1.1.0 of the Splunk Add-on for EMC VNX has the following known issues:

Publication date Defect number Description
N/A N/A Due to the changes to the add-on file name and corresponding folder structure that occurred with version 1.0.1, this version of the add-on will not replace version 1.0.0. If you are migrating from 1.0.0 directly to 1.1.0, see the migration notes above.

Third-party software attributions

Version 1.1.0 of the Splunk Add-on for EMC VNX does not incorporate any third-party software or libraries.

Version 1.0.1

Version 1.0.1 of the Splunk Add-on for EMC VNX is compatible with:

Splunk Enterprise versions 6.1
CIM 4.1, 4.0, 3.0
Platforms Platform independent
Vendor Products EMC VNX series

Migration from Version 1.0.0 to 1.0.1 or later

If you have version 1.0.0 of the Splunk Add-on for EMC VNX already installed, note that version 1.0.1 will not update or replace your current installation. Because the file name and folder structure were updated for this release to match standard naming structure, the add-on behaves as a new installation, not an upgrade.

Version 1.0.1 changes the folder name, sourcetype names, and default index behavior. Review your local app.conf, props.conf, and indexes.conf and make any appropriate changes.

To migrate from version 1.0.0 to 1.0.1:

  1. Download and install version 1.0.1 of the add-on
  2. Disable version 1.0.0 in Splunk Enterprise
  3. Enable version 1.0.1 of the add-on
  4. Create and adjust your local conf files as needed to match your old configurations
  5. Verify your configurations work as expected
  6. Delete version 1.0.0 of the add-on

New features in Version 1.0.1

Version 1.0.1 of the Splunk Add-on for EMC VNX includes the following new features: N/A

Fixed issues in Version 1.0.1

Version 1.0.1 of the Splunk Add-on for EMC VNX fixes the following issues:

  • events now routed to main index by default (ADDON-1952)
  • add-on filename, sourcetype names, and folder structure now matches standards (ADDON-2001)

Known issues in Version 1.0.1

Version 1.0.1 of the Splunk Add-on for EMC VNX has the following known issues:

  • Due to the changes to the add-on file name and corresponding folder structure, this version of the add-on will not replace any prior versions. See the migration notes above.

Third-party software attributions for Version 1.0.1

Version 1.0.1 of the Splunk Add-on for EMC VNX does not incorporate any third-party software or libraries.

Version 1.0.0

Version 1.0.0 of the Splunk Add-on for EMC VNX has the same compatibility specifications as Version 1.0.1.

New features in Version 1.0.0

N/A

Fixed issues in Version 1.0.0

  • incorrect timestamping of some sources (ADDON-1616)
  • some fields not transferred successfully (ADDON-1620)
  • source mapping incorrect (ADDON-1632)
  • fields "cpu_count" and "vendor" under source "vnx_block_agent" missing (ADDON-1633)
  • duplicated ip addresses in inputs.conf causes errors (ADDON-1629)
  • version displays incorrectly (ADDON-1627)
  • some events with source "vnx_block_device" lost with 60 second collection duration for "vn_block_inventory" (ADDON-1658)
  • incorrect configurations in props.conf (ADDON-1628)
  • errors with ssh on Windows Server 2008 (ADDON-1668)
  • indexing errors when VNX connection is down (ADDON-1667)
  • CIM mapping failure for "storage" field in sourcetype "vnx:file:fileSystem" (ADDON-1941)

Known issues with Version 1.0.0

  • events not written to the main index by default (ADDON-1952)
PREVIOUS
Release notes for the Splunk Add-on for EMC VNX
  NEXT
Hardware and software requirements for the Splunk Add-on for EMC VNX

This documentation applies to the following versions of Splunk® Supported Add-ons: released


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters