Cisco UCS not collecting data

[robertbarton]

I have recently installed the Splunk app for Cisco UCS and am having trouble getting data. The installation seemed simple enough, I edited the credentials.csv and managers.csv files for the Splunk_TA_CiscoUCS with the correct format, as outlined in the readme and then copied the apps into /opt/splunk/etc/apps (single-server). the ucs-authentication_domain_name is correct as is the user and password (tested with ssh) and the UCS manager can communicate with the splunk server.

After restarting the splunk service the app itself is available, but data is unavailable.

I have manually run the python Collect.py script with the options outlined in the inputs.conf with no errors at all.

python /opt/splunk/etc/apps/Splunk_TA_CiscoUCS/bin/Collect.py faultInst

python /opt/splunk/etc/apps/Splunk_TA_CiscoUCS/bin/Collect.py equipmentFex equipmentIOCard equipmentSwitchCard equipmentChassis equipmentPsu computeBlade computeRackUnit fabricDceSwSrvEp etherPIo fabricEthLanEp fabricEthLanPc fabricEthLanPcEp fabricVlan fabricVsan lsServer vnicEtherIf vnicFcIf storageLocalDisk firmwareRunning statsCollectionPolicy]

python /opt/splunk/etc/apps/Splunk_TA_CiscoUCS/bin/Collect.py topSystem equipmentChassisStats computeMbPowerStats computeMbTempStats processorEnvStats equipmentPsuStats adaptorVnicStats etherErrStats etherLossStats etherRxStats etherPauseStats etherTxStats swSystemStats]

and still do not see data. There doesn't seem to be any useful info in any of the log files to point me in the right direction.

Has anyone has any experience with this, and managed to get it working with data? If so, did you have to perform any additional steps other than those outlined in the readme file?

I'm new to splunk, so it is possible there is somewhere i am not checking that i might not be aware of.

[lisaac]

I ran into this same issue with the misshing "header", and note that the "username" field in the credentials.csv file is case sensitive. Well, it was in my case.

[halr9000]

I do plan on adding more logging to catch things like this.

[Glenn · Accepted solution]

The problem was that you were missing the "header" lines at the top of the managers.csv and credentials.csv files. This mean that the dictReader method that pulls the manager and credential information out of the files was not finding its expected fields and so was not reading anything into the list of managers. So, when it came down the part of the script "## Let's get down to business:" (the action part of the script), the array of managers is empty and it exits straight away (silently).

Adding the headers "server,realm" (managers.csv) and "realm,username,password" (credentials.csv) as per the examples in the README.md meant the script now reads the managers, and collects the information as expected.

I was only able to solve this as I had access to your config, the problem was not present in the question above.

[robertbarton]

Forgot to mention, Using Linux, not Windows