Cisco Unified Border Element (CUBE)

Note this setup is surprisingly unlike how the CDR is collected from CUCM. We apologize for Cisco’s inconsistency.

Preparation

First upgrade the TA_​cisco_​cdr app on your forwarder(s) to the latest version . 

Next upgrade to the latest version of the Cisco CDR and Canary apps if you haven’t already.

Next you will need to set up an FTP server. CUBE and vCUBE cannot use SSH or SFTP, so the SFTP server you may have set up already to collect Callmanager’s CDR can not be used for the CUBE data.

On your FTP server, create a user and a new folder that the user can write files to. For our example setup, we will be using server 10.0.0.100, and a user user with password splunk. As our prefix for filenames, we will use cube_​.

Validation steps:

After this is set up, you should be able to confirm via a manual test that this user can upload a file to the configured directory. Remember to delete the test file(s) when you are done.

Steps to configure the file accounting server

Log into the router with an account with administrative permissions. Then, run the below listed commands to set up gw-accounting to file, change the cdr-format to ​“detailed”, configure the FTP server information, and tell the system to flush new data to file once per minute. 

In the below, adjust 10.0.0.1 to be the IP/​dns name of your ftp server and the ftpusername and ftppassword to be the username and password for the ftp user. The cube_​ that’s after the IP address in the example should also be in your command, it prefixes the files that are being written with the word ​“cube” and an underscore so we can more easily identify them in the next step, creating the input.

enable
configure terminal
gw-accounting file
cdr-format detailed
primary ftp 10.0.0.1/cube_ username ftpusername password ftppassword
maximum cdrflush-timer 1
end

This configuration accepts many of the default settings for buffer sizes and the number of reattempts. If you have any troubles at this layer, or if you’d like to confirm those settings more thoroughly, please see Cisco’s documentation on configuring file accounting.

Create a new Splunk input

We will now create a new ​“batch” input for the CUBE CDR files, similar to the ones you created for CUCM CDR and CMR.

Important note: this input will be set up to delete the files from disk as they go into Splunk. If you need this to not happen, please see the notes at the end of this section.

All these steps happen in your FTP server’s Splunk Universal Forwarder’s configuration files:

1) Create the monitor input by adding this config to an inputs.conf file located at “$SPLUNK_​HOME/​etc/​apps/​TA_​cisco_​cdr/​local/inputs.conf”. This file should exist already, but if it does not, you may need to create the folder ​“local” and the file itself. Make sure the user Splunk runs under has permissions to this file and folder.

If your Universal Forwarder is on Windows, the contents of your inputs.conf will look like this:

[batch://D:\path\to\files\cube_*]
index = cisco_cdr
sourcetype = cube_cdr
move_policy = sinkhole

If your Universal Forwarder is on Linux or Unix, the input will look like this:

[batch:///path/to/files/cube_*] 
index = cisco_cdr
sourcetype = cube_cdr 
move_policy = sinkhole 

It is critical that no mistakes be made here. Only the path (after ​“batch://”) and possibly the index need editing. All else should be left exactly as it is. Use the examples as a reference to make sure you are using the right number and direction of slashes/​backslashes, too. 

NOTE: As mentioned above, this is a sinkhole input, and it will delete each file matching the filename ube_​* as it indexes it. Any existing csv files that exist in this directory that start with cube_​will be indexed and deleted almost immediately, and any new files written to here will be indexed and deleted as they arrive. If you have other intentions for these files besides putting them in Splunk, please contact us, and we can help you come up with another solution.

Next Steps

Contact us to set up a Webex! We can help confirm everything is working properly and help you start using this data.

If you have any comments at all about the documentation, please send them to docs@​sideviewapps.​com.