Using the BMC Performance Assurance UDR Collection Manager (UCM) Status Reports

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    TrueSight Capacity Optimization


    Capacity Optimization


    All version



      The UDR Collection Manager (UCM) Status Reports provide a central web-based reporting tool regarding Perform data collection and data transfer. By default the reports are updated with the current collection status every 15 minutes and include historical collect and transfer information for the previous 7 days.  




    Legacy ID:KA286462

      To view the UCM status reports, open a web browser on your Unix console and navigate to the following URL:  
    It is also possible to share the UCM Status Reports via a web server installed on the Perform console but that is beyond the scope of this document.  
    In the left window pane the UCM Status Reports list each Manager run by date and reports the 'worst' status of any node contained within that run via a red, yellow, or green icon.  
    In this sample screenshot there are 2 Manager runs scheduled 'vm' and 'remedy_daily' and data collection is being reported in 'warning' status but both runs are reporting in 'error' status for the previous days.  
    Selecting the 'vm' Manager run lists each of the computers associated with that run in the main UCM status reports pane. Here we can see that of 6 machines, 3 are properly collecting data and 3 have 'Failed to Send collect request, will retry'. A failure to send a collection request is reported as a Warning because UCM is still retrying the collection requests (by default once every 15 minutes). The collection request won't transition to 'error' state until UCM stops attempting to re-try the data transfer (which, by default, happens after 90% of the collection interval elapses or some time after 9:30 PM for a 24 hour collection run).  
    Drilling down further into computer 'epa-vm-01' we can see that the reason data collection is failing is a "Service daemon connection timed out (node offline, firewall, or non-responsive app)" error. This could mean the machine is off-line (which happens to be the case here) or a firewall is blocking the connection, or something else like that.  
    Drilling down further into computer 'epa-vm-04' we can see that the reason data collection is failing is a "Service daemon not installed on the remote node (connection refused)" error. This could mean that the Perform product isn't installed on the machine or that the Service Daemon isn't listening on port 10128 for some reason. This message means that the connection to the Service Daemon on port 10128 is failing with a 'Connection Refused' rather than simply timing out.  
    After fixing the Perform Agent installation on the 'epa-vm-04' machine the Collect status remains in 'Warning' state but now we can see that data collection is working on the machine since the "Collection" table showing the number of Configured, Active, and Terminated groups is not populated with data. The reason the machine is listed in warning state is that some of the configured metric groups are not being collected on the machine. For information on how to use the 'UCM Status Filtering' option to change the collection status from yellow to green see    Resolution 15063344 - "How can I change nodes with missing metric groups from Warnings to OK state in UDR Collection Manager (UCM) status reports?".  
    Once the groups we expect to not be collected have been filtered the UCM Status Reports will show the machine in green OK status and will list the count of 'Terminated No Data' groups that have been filtered.  
    We can also use the UCM Status Reports to identify and resolve data transfer problems. For example, looking at the 'vm' group for the previous day one can see that although the 'epa-vmsc-01' machine successfully collected data the data transfer failed.  
    Drilling down into that machine we can see that the data transfer is failing with the error, "Collect Request - Collect still active unable to transfer". That message means that when the Perform console was trying to transfer data the remote agent was still actively collecting data for that collection request. That message generally means that the time on the remote node is incorrect resulting in data transfer still running after it should have stopped. In this case the time on the remote node is incorrect to the point where data collection is still active even after the transfer duration has elapsed (resulting in no data being transferred for that machine).  
    The UDR Collection Manager Status Reports are the single most useful source of information regarding Perform data collection and data transfer. The UCM Status Reports can be used to quickly identify which nodes are failing to collect or transfer data and the failure messages can be used to narrow the problem down to a small set of likely root causes.  
    Related Products:  
    1. BMC Performance Assurance for Servers
    3. BMC Performance Assurance for Virtual Servers


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles