Cisco AnyConnect Network Visibility Module (NVM) App for Splunk consists of 2 components:
• The Collector Component which is responsible for collecting and translating all IPFIX (nvzFlow) data from the endpoints and forwarding it to the Splunk App. This is a manually installed add-on for Splunk Enterprise.
• The Splunk App with pre-designed Dashboards to view and analyze the data.
The Application should be installed on the Search Head or Indexer, either through the UI via “Manage Apps” or by extracting the archive into /opt/splunk/etc/apps folder. Please restart the Spunk Server after installation is completed.
After completing this step, refer to the collector installation section below. The collector must be running before data will be available to the Splunk application.
The default configuration receives two data feeds for Splunk, Per Flow Data and Endpoint Identity Data, on UDP ports 20519 and 20520 respectively. This can be changed in the Application Input settings in Splunk if for some reason you needed to change the collector configuration as described below.
The collector runs on 64-bit Linux. CentOS and Ubuntu configuration scripts are included. The CentOS install scripts and configuration files can also be used in Fedora and Redhat distributions as well.
The collector should be run on either a standalone 64-bit Linux system or a Splunk Forwarder running on 64-bit Linux. The solution can also be run on a single 64-bit Linux system that includes both the collector and Splunk Enterprise for demonstration purposes.
In order to install the collector you will need to copy the application in the CiscoNVMCollector_TA.tar file, located in the $APP_DIR$/appserver/addon/ directory to the system you plan to install it on.
Extract the tar file on the system where you plan to install the collector on and execute the install.sh script with super user privileges. It is recommended to read the $PLATFORM$_README file in the .tar bundle before executing the install.sh script. The $PLATFORM$_README file provides information on the relevant configuration settings that need to be verified and modified (if necessary) before the install.sh script is executed. At a minimum, you will need to configure the address of the Splunk instance you will be forwarding data to. Failing to properly configure the system can cause the collector to operate incorrectly.
A collector can handle a minimum of 5000 flows per second on a properly sized system.
The collector needs to be configured and running before the Splunk App can be used.
By default, the collector receives flows from AnyConnect NVM endpoints on UDP port 2055.
Additionally, the collector produces two data feeds for Splunk, Per Flow Data and Endpoint Identity Data, on UDP ports 20519 and 20520 respectively.
Both the receive and data feed ports can be changed by altering the acnvm.conf file and restarting the collector instance. Make sure that any network firewalls between endpoints and the collector or between the collector and Splunk system(s) are open for the configured UDP ports. Also ensure that your AnyConnect NVM configuration matches your collector configuration. Refer to the AnyConnect Administration Guide for more information.
Once both components are installed and running, refer to the Help files section from within the Splunk application for detailed information about the pre-configured reports, data model and information elements that are created by the solution.
After initial setup, you may need to restart one of your AnyConnect endpoints to ensure the initial IPFIX templates are sent to the collector.
Some additional information is available at this Cisco Community Site that you might find useful.
Splunk Developers who are interested in learning more about the AnyConnect NVM protocol and overall solution can go to the Cisco DevNet site for more information.
This app is written and maintained by Cisco (nvzFlow at cisco dot com). No official support is available. Be sure to read the above sections for initial assistance with setup and configuration. See Supplemental End User License for more information.
Adds fes and fss (flow start and end time) fields for seconds since epoch
Add preload templates for nvzflow3
Added filtering capabilities for collector.
Improved concurrency support for collector.
Added support for Kafka export.
Added plugin framework to extend export capabilities.
For more information, to see the Help->User Guide in the Splunk app.
Fixed collector incompatibility.
Add Network Interfaces dashboard.
Add application-specific metrics to the Applications dashboard.
Cisco AnyConnect Network Visibility App for Splunk. Copyright © 2015 Cisco Systems Inc. All rights reserved.
Splunk's App Certification program uses a specific set of criteria to evaluate the level of quality, usability and security your app offers to its users. In addition, we evaluate the documentation and support you offer to your app's users.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.