Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Unable to collect data from a Cisco UCS Manager 2.2 instance in SRM Suite 3.0The following conditions, events or system behaviors may be observed with this issue: Data collections are failing to run after the Cisco UCS SolutionPack has been configured in SRM Suite to collect data from a UCS Manager 2.2 instance.Collection log for SRM Suite Cisco UCS SolutionPack shows no connection errors, but no data is being returned in the collection processAs shown in the following example, there are no connection-related errors seen in the collection log file (/opt/APG/Collector-Manager/cisco-ucs/logs/collecting-0-0.log) for the UCS SolutionPack when data collection runs: INFO -- [2014-02-04 16:07:35 CET] -- TimedPollingTask::run(): Starting polling task "topSystem"... INFO -- [2014-02-04 16:07:35 CET] -- i::run(): Starting XML parsing job for collecting configuration topSystem and context UCS0... INFO -- [2014-02-04 16:07:35 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- i::a(): topSystem: Done. INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- UcsWebServiceExecutor::close(): Session was successfully closed INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Polling task "topSystem" completed in 59 ms. INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Starting polling task "equipment.Chassis"... INFO -- [2014-02-04 16:07:36 CET] -- i::run(): Starting XML parsing job for collecting configuration equipment.Chassis and context UCS0... INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- i::a(): equipment.Chassis: Done. INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- UcsWebServiceExecutor::close(): Session was successfully closed INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Polling task "equipment.Chassis" completed in 70 ms. INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Starting polling task "equipment.Fabric"... INFO -- [2014-02-04 16:07:36 CET] -- i::run(): Starting XML parsing job for collecting configuration equipment.Fabric and context UCS0... INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- i::a(): equipment.Fabric: Done. INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- UcsWebServiceExecutor::close(): Session was successfully closed INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Polling task "equipment.Fabric" completed in 61 ms. INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Starting polling task "ether.PIo"... INFO -- [2014-02-04 16:07:36 CET] -- i::run(): Starting XML parsing job for collecting configuration ether.PIo and context UCS0... INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- i::a(): ether.PIo: Done. INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- UcsWebServiceExecutor::close(): Session was successfully closed INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Polling task "ether.PIo" completed in 62 ms. INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Starting polling task "fc.PIo"... INFO -- [2014-02-04 16:07:36 CET] -- i::run(): Starting XML parsing job for collecting configuration fc.PIo and context UCS0... INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- i::a(): fc.PIo: Done. INFO -- [2014-02-04 16:07:36 CET] -- SOAPXmlRequestExecutor::executeCommand(): Successfully connected to host : xxx.xxx.xxx.xxx . INFO -- [2014-02-04 16:07:36 CET] -- UcsWebServiceExecutor::close(): Session was successfully closed INFO -- [2014-02-04 16:07:36 CET] -- TimedPollingTask::run(): Polling task "fc.PIo" completed in 78 ms. While the collecting log shows no connection issues connecting to the UCS Manager host, a file collection shows that no data is being returned in the collected data as shown in the following example: (r)1391526156: group::Cisco-UCS-Collectorxxx.xxx.xxx.xxx Uptime({unit=s, host=xxx.xxx.xxx.xxx , datagrp=Cisco-UCS-topSystem, source=Cisco-UCS-Collector, name=Uptime, uptime=NaN, device=, ucsname=, devtype=UCS Manager})=NaN1391526456: group::Cisco-UCS-Collectorxxx.xxx.xxx.xxx Uptime({unit=s, host=xxx.xxx.xxx.xxx, datagrp=Cisco-UCS-topSystem, source=Cisco-UCS-Collector, name=Uptime, uptime=NaN, device=, ucsname=, devtype=UCS Manager})=NaN
The above issue has been found to occur because there is an authentication issue. Specifically, this issue can occur when the user used for the UCS SolutionPack data collection is a local user account, but it is entered in the format of DOMAIN\USER instead of USER. In this condition, SRM Suite does not report any error but authentication fails on the Cisco UCS Manager side.Completing the following steps can confirm the cause of this authentication issue: Connect to the Cisco-UCS Collector Host in the SRM Suite through the command line.Change (cd) to CISCO-UCS directory: cd /opt/APG/Collecting/XML-Collector/cisco-ucs/conf/CISCO-UCS Run the following command: wget http://xxx.xxx.xxx.xxx:80/nuova --post-file=request-cseries-auth.xml Error code 200 returned.In the nuova file returned, the following was seen when the file was opened using the "cat nuova" command: <aaaLogin cookie="" response="yes" errorCode="551" invocationResult="unidentified-fail" errorDescr="Authentication failed"> </aaaLogin> Check if the user can log in to the Cisco UCSM User Interface: Unsuccessful.This confirms that the user account used is a local account and not an Active Directory account.
To address this and other user authentication issues with the Cisco UCS SolutionPack of the SRM Suite, do the following: In SRM Suite 3.0, go to Centralized Management > SolutionPack > Infrastructure.Edit the Cisco UCS SolutionPack to use a user account which is able to login succesfully to the UCS Manager user Interface.Click Reconfigure to save the changes.Data should now be collected for the Cisco USC Manager system.
Note: if the following message is returned when executing the wget:<error cookie="" response="yes" errorCode="ERR-secondary-node" invocationResult="1" errorDescr="UCSM is not available on secondary node"/>That is an indication that the UCS is setup as a failover node, meaning it becomes actives only in the event another UCS node goes down, and Watch4net cannot actively monitor that node.