Installation and use of this app signifies acceptance of the Gigamon End User License Agreement(EULA) inclusive of any future updates.
Navigate to the Gigamon and Stream Integration section for a step-by-step installation path.
This app GigamonMetadataForSplunk replaces the old app GigamonIPFIXMetadataForSplunk Ver 1.1.0. It isrecommended to uninstall/remove the old app GigamonIPFIXMetadataForSplunk before installing this app, GigamonMetadataForSplunk.
Gigamon Metadata Application For Splunk allows a Splunk Admin the ability to configure Splunk Stream for Gigamon Specific elements over IPFIX or CEF.
There are no included scripts.
These are the improvements packaged as part of version 1.2.1. * Minor fixes to get this app certified by Splunk * Added Demo & Tutorial dashboard
These are the improvements packaged as part of version 1.2.0. * Widgets are rearranged in such a way that Metadata Overview tab lists the widgets for all traffic types such as SSL, DNS, HTTP and HTTPS * Advanced metadata details for DNS, SSL and HTTP/HTTPS are put under Metadata Dashboards tab * Shanon Entropy values are calculated for URL Domains and DNS Domains * Some of the new widgets added are: TLS Versions seen, List of DNS Servers Seen, SSL Certificate Heatmap, Self Signed Certificates, SSL Certificates which expired or expiring soon and more
These are the improvements packaged as part of version 1.1.0.
New Feature
Bug
Version 1.2.1 of Gigamon Metadata Application For Splunk is compatible with:
Item | Value |
---|---|
Splunk Enterprise versions | 6.5, 6.6, 7.0.0, 7.1.1, 8.x.x |
Splunk Stream versions | 7.0.1, 7.1.x |
URL Toolbox | 1.6 |
CIM | 4.9 |
Platforms | <Platform independent> |
Vendor Products | GigaVUE-OS >=5.3 with GigaSMART |
NOTE:
Gigamon Metadata Application For Splunk requires Splunk Stream 7.0.1 or 7.1.x to ingest IPFIX data. It is not compatible with Splunk Stream 7.2.x and 7.3.x.
Splunk Stream is not required to ingest CEF data.
Gigamon Metadata Application For Splunk includes the following new features:
Version 1.2.1 of Gigamon Metadata Application For Splunk fixes the following issues:
Version 1.2.1 of Gigamon Metadata Application For Splunk has the following known issues:
splunk_app_stream
vocabulary file will be deleted. This needs restored with the correct version of the vocab.splunk_app_stream
stream file will be deleted. This needs restored with the correct version of the stream.metadata
vs packet
) requires the deletion and re-addition of the configured netflow stream.netflow
stream file is changed, any existing streams using that stream configuration need to be deleted and re-added.Access questions and answers specific to Gigamon Metadata Application For Splunk at https://answers.splunk.com.
Support Email: apps@gigamon.com
Please visit https://answers.splunk.com, and ask your question regarding Gigamon Metadata Application For Splunk. Please tag your question with the correct App Tag, and your question will be attended to.
Because this add-on runs on Splunk Enterprise, all of the Splunk Enterprise system requirements apply.
Because this add-on requires Splunk Stream, all of the Splunk Stream system requirements apply.
Download Gigamon Metadata Application For Splunk at Splunkbase.
https://splunkbase.splunk.com/app/3908/
Follow these steps to install the app in a single server instance of Splunk Enterprise:
Gigamon Metadata Application For Splunk has dependency on the app “URL Toolbox”. Install the Splunk app “URL Toolbox” using the standard installation procedure. “URL Toolbox” can be found on splunkbase.splunk.com.
Here is an example output of inputs.conf file
[udp://10514]
connection_host = ip
sourcetype = cefevents
10514 above is the port number. Change it to whatever the port number desired. Make sure that it matches with port number configuration on GigaSMART device.
The Gigamon and Stream integration requires precise adherence to the instructions. Failure to do so may cause Stream to not collect the Gigamon IPFIX data appropriately.
The GSI (Gigamon and Stream Integration) is an advanced configuration technique, designed to extend the protocol decoding abilities of Splunk Stream. As this feature relies on Splunk Stream, Splunk Stream is a requirement and must be installed on your Splunk server(s). Please see the instructions on how to install Splunk Stream.
If you are installing Stream for the first time, the preferred version at this time is 7.1.0
. If you have an existing stream installation, ensure the version number is 7.0.1
or 7.1.0
(other versions, if available, have not been tested).
NOTE: The NIC associated with the Netflow collection should not be in promiscuous mode. Stream is being used as a protocol decoder in this configuration only.
In order to extend the base installation of Stream, there must be file-level changes made. This is a Manual Configuration. The base location of the Gigamon-specific configuration is $SPLUNK_HOME/etc/apps/GigamonMetadaForSplunk/appserver/static/library
. $SPLUNK_HOME
refers to the install location of Splunk. Start in the library folder mentioned, and then proceed to either Manual Configuration.
This configuration method requires the user to edit and copy various files to locations in the splunk_app_stream
and Splunk_TA_stream
apps. $SPLUNK_HOME
refers to the install location of Splunk.
$SPLUNK_HOME/etc/apps/GigamonMetadaForSplunk/appserver/static/library/gigamon_streamfwd.conf
to change the reciever IP and Port to your local settings (replace @@IP
and @@PORT
).$SPLUNK_HOME/etc/apps/GigamonMetadaForSplunk/appserver/static/library/gigamon_streamfwd.conf
to $SPLUNK_HOME/etc/apps/splunk_app_stream/local/streamfwd.conf
and $SPLUNK_HOME/etc/apps/Splunk_TA_stream/local/streamfwd.conf
Open up the File and modify the gigamon_vocabulary file to match the version of the Splunk Stream.
Copy the Splunk Stream Version-specific vocabulary file (see file names right below) to $SPLUNK_HOME/etc/apps/splunk_app_stream/default/vocabularies/gigamon.xml
and $SPLUNK_HOME/etc/apps/Splunk_TA_stream/default/vocabularies/gigamon.xml
.
Copy $SPLUNK_HOME/etc/apps/GigamonMetadaForSplunk/appserver/static/library/gigamon_stream.json
to $SPLUNK_HOME/etc/apps/splunk_app_stream/default/streams/netflow
.
$SPLUNK_HOME/etc/apps/splunk_app_stream/local/props.conf
file.[stream:netflow]
, add this line of configuration: SEDCMD-remove_nulls_gigamon = s/\\u0000//g
. If the stanza doesn't exist, create it.SEDCMD
will remove any data that cannot be decoded correctly.Full and complete documentation of Stream Configuration is located at docs.splunk.com. This instructions use Stream 7.1.0 as the basis, but instructions for Stream 7.0.1 are available as well at Stream 7.0.1 - User Manual - Configure Streams.
No
Now that Stream is configured to accept Gigamon Elements, configure the Gigamon appliance that has the GigaSMART card installed. Gigamon provides documentation to configure netflow and metadata generation, and there is also a third-party step-by-step tutorial that may help configure the GigaSMART.
NOTE: There is an option within the GigaSMART Exporter configuration to set the Template Refresh Interval
. This setting should be set to AT MOST 2 minutes.
If you are pushing Splunk_TA_stream
to a universal forwarder in a distributed deployment, then you must make the same changes for Splunk_TA_stream
above in the deployment-apps
folder
When upgrading Stream:
splunk_app_stream
vocabulary file will be deleted. This needs restored with the correct version of the vocab.splunk_app_stream
stream file will be deleted. This needs restored with the correct version of the stream.metadata
vs packet
) [Splunk Stream 7.0.1 -> 7.1.x] requires the deletion and re-addition of the configured netflow stream.If the netflow
stream file is changed, any existing streams using that stream configuration need to be deleted and re-added.
This app provides the index-time and search-time knowledge for the following types of data:
The following lookups are provided as a part of the Gigamon Metadata Application For Splunk app.
Gigamon Metadata Application For Splunk does make use of an event generator. This allows the product to display data, even when there are no inputs configured. Edit eventgen.conf
for each stanza to "enable" the stanza.
This generates relevant fields to the IPFIX IANA HTTP elements.
This generates relevant fields to the IPFIX IANA SSL elements.
This generates relevant fields to the IPFIX IANA DNS elements.
Update Eventtype
button, and the Save
button.The best place to start troubleshooting Gigamon Metadata Application For Splunk is to visit the Monitoring Console Health Check. There are 4 specific checks related to the Gigamon Stream configuration.
Click the "Start" button and then review the results.
If you are still having problems, use the Command line and run this command:
$SPLUNK_HOME/bin/splunk diag --collect app:GigamonMetadaForSplunk
Send the generated diag file to Gigamon Metadata Application For Splunk support.
Summary Indexing: None
Data Model Acceleration: None
Report Acceleration: None
Upgrade Gigamon Metadata Application For Splunk by re-installing into your environment per Splunk Documentation and your environment (see steps above).
Gigamon Metadata Application For Splunk incorporates the third-party software or libraries referred at the path $SPLUNK_HOME/etc/apps/GigamonMetadaForSplunk/appserver/static/html/3pp.md
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.