Updating the Cisco CDR Reporting and Analytics app is usually quick and easy.
Recap: You are either a customer with a full license, or a prospect evaluating the app and using a trial license.
You are here to either a) update your production build to the latest maintenance release, b) upgrade from the trial version to the full version, or c) update your trial version with a newer trial version. You’ve also reviewed the Release Notes, Admin Manual, made backups, etc….
Updating the Cisco CDR Reporting and Analytics app
If your Splunk server has internet access
Open up your Splunk, log in as an administrator, and in the apps list click the gear icon, or on some pages Manage Apps.
Search for “sideview” in your apps. This should bring up a list of several apps:
Cisco CDR Reporting and Analytics
For each that has an update waiting, click the “Update to X.X.X” link and follow the instructions (preferably in the order listed above).
NOTE: if you’re updating from a very old version and do not have the Canary app installed yet, take a brief detour back to our install docs to fix that.
If your Splunk server does NOT have internet access
Visit these pages and click Download to download the following apps to your local system as tar.gz files.
Use Gunzip and tar, or an application like Winzip, to uncompress the .tgz file.
With 7‑zip on Windows …
Right-click on the file, select 7‑zip -> “Open Archive”
Drill down until you see a folder called “TA_cisco_cdr”
Drag/Extract that folder to a temporary location on your system.
With gunzip or tar, we’re not giving any hints unless you ask specifically. We figure you wouldn’t be using those utilities unless you knew how to use them. 🙂
Copy the TA_cisco_cdr directory into $SPLUNK_HOME/etc/apps/on your forwarder host.
Restart the Splunk instance on your forwarder host.
WARNING – Do not overwrite your specific inputs.conf file! Your specific inputs and configurations *should* be stored in a directory “TA_cisco_cdr/local/”, and if it is, we won’t overwrite those. But better to check than to have to restore configurations later!
Not that we expect problems, but Splunk is a complex system, and all sorts of interesting things can go wrong.
The majority of the time if there’s anything wrong it’s just that your browser is caching things it shouldn’t and using old copies of updated files. Please try clearing your browser cache (instructions vary based on your browser – Google is your friend), and check again. Also, try to reproduce the problem in Incognito mode or a new Private Window, depending on your browser. If that doesn’t resolve your problems, please contact us for help or email [email protected]sideviewapps.com!
The other issue we find is that after updating both apps, you may get a screen telling you “Page not found”.
This is a bug in Splunk that we’re currently helping them to chase down. It’s not serious and is only some misdirection on the part of the update page. Just click the “here” in the middle, and everything will be fine!