TrueSight Capacity Optimization(TSCO) - How do I determine the patch level and version of a Gateway or BMC Performance Assurance (BPA) Console Server and  Agent?

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.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    BMC Performance Assurance for Servers, TrueSight Capacity Optimization



    QUESTION:

     
       How can I tell which patch level has been applied to the Perform installations in my environment?   
       
        
         
    • TrueSight Capacity Optimization 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0 
    •    
    • BMC Performance Assurance for Virtual Servers  9.59.0.00, 7.5.10, 7.5.00
    •    
    • BMC Performance Assurance for Servers  9.59.0.00, 7.5.10, 7.5.00
    •   
       
       
        
         
    • Unix or Windows
    •   
       


    ANSWER:

     

    Section I: TrueSight Capacity Optimization 10.3 and later

    When data from the TSCO Agent is imported into the TSCO database via the TSCO Gateway Server ETL the AGENT_PACKAGE_BUILD_DATE and AGENT_PACKAGE_VERSION metrics will be imported for each entity that is loaded into TSCO.  The AGENT_PACKAGE_VERSION will report the TSCO Agent version and patch level (for example, 10.7.00.CP0.CHF0 for TSCO Agent version 10.7.00 with no patches). 

    A Configuration Metrics report (or query) could be created that will report the AGENT_PACKAGE_VERSION configuration metric associated with each entity which can be used to determine the current TSCO Agent patch level installed on each machine. 

    This information is available in TSCO for all platforms supported by the TSCO Gateway Server VIS parser ETL (this includes VIRTUAL computer types where a collector is installed within the guest (such as 'Virtual Node - VMware' which is the entity type for VMware guest machines running a collector within the guest OS). 

    When older versions of the TSCO Agent are processed through a TSCO 10.3.00 or later Gateway Server they will still report the AGENT_PACKAGE_VERSION but it will only contain the base TSCO Agent release version (since the '[NT] Collector Information') group in the UDR data doesn't contain the additional fields necessary to report the detail AGENT_PACKAGE_VERSION. 
       

    Section II: Perform version 7.5.00 and later (including TrueSight Capacity Optimization 10.0 through 10.7)

      
       
        

    There are a few methods for determining the patch levels of the components when the console is 7.5.00 or later.

        

    Via the Visualizer Graphics client

        

    Both the agent and console patch level are recorded in the Visualizer database along with the performance metrics for each server.  

        

    (a) For physical servers, use

        

    Graphics -> Physical System -> Performance Data Sources Metrics 

        

    (b) For partitions (such as AIX, HP) , use

        

    Graphics -> Virtualized Host -> Partition Performance Data Sources Metrics

        

    If the chart is not listed in Visualizer, see KA357032: How can I obtain the latest vgd file(s) for Visualizer developed for Distributed Systems by BMC? for information on how to download an updated cpaix.vgd file.

        

     

        

    Via the Visualizer file

        

    The collector and agent build information is available in the Input ".vis" file(s) under the AGENTS and CMPNTS section.  For example:

        
        T;AGENTS    
    ;'bgscollect','7.5.00','Jun 27 2010',,    
    <--snip-->    
    T;CMPNTS    
    ;'BPA Analyze','7.5.00','Jul 12 2010'   
        

    For the console version there will only be one value reported -- but for the agent versions each entry in the AGENTS table is mapped to a specific system via the dyamic table section of the file (for example the PHYSD section).  This means that it is easier to detect the console version and the list of agent versions deployed across the computers contained in that Visualizer file than the agent version installed on a particular machine via the file.

        

     

        

    Via SQL run against the Visualizer database

        

    SQL like the following could be used to extract the necessary information for standalone systems (tables are CAXAGENT and CAXCMPNT). Be sure to change the date range you are interested in.

        
    Standalone systems
        

    SELECT
        CAXINTVL.Int_start_date, count(*) as "Number_of_Intervals", CAXPSYS.Host_Name, CAXPSYS.operating_system_name
      , CAXPSYS.operating_system_version, CAXPSYS.Domain, CAXPSYS.Policy, CAXCMPNT.Component_Name, CAXCMPNT.Component_Version
      , CAXAGENT.Collector_Name, CAXAGENT.Collector_Version, CAXAGENT.Collect_Mode, CAXAGENT.Proxy_Node
    FROM
      CAXPSMD, CAXPSYS, CAXINTVL, CAXCMPNT, CAXAGENT
    WHERE
      Int_start_date between '09/09/07' AND '09/09/10'
      AND CAXPSMD.PHYSS = CAXPSYS.INDEXX
      AND CAXPSMD.AGENTS = CAXAGENT.INDEXX
      AND CAXPSMD.CMPNTS= CAXCMPNT.INDEXX
      AND CAXPSMD.INTVL = CAXINTVL.INDEXX
    GROUP BY
        CAXINTVL.Int_start_date, CAXPSYS.Host_Name, CAXPSYS.operating_system_name, CAXPSYS.operating_system_version
      , CAXPSYS.Domain, CAXPSYS.Policy, CAXCMPNT.Component_Name, CAXCMPNT.Component_Version, CAXAGENT.Collector_Name
      , CAXAGENT.Collector_Version, CAXAGENT.Collect_Mode, CAXAGENT.Proxy_Node
    ORDER BY
      CAXINTVL.Int_start_date, CAXPSYS.Host_Name;

        
    Partitioned systems
        

    For partitioned systems (such as AIX frames or Solaris LDOMs) the following SQL can be used instead:

        

    SELECT
        CAXINTVL.Int_start_date,count(*) as "Number_of_Intervals"
      , CAXVM.Virtual_Type
      , CAXVM.Partition_Name
      , CAXVM.Operating_System_Name
      , CAXVM.Operating_System_Version
      , CAXAGENT.Collector_Name
      , CAXAGENT.Collector_Build_Date
      , CAXAGENT.Collector_Version
      , CAXCMPNT.Component_Name
      , CAXCMPNT.Component_Build_Date
      , CAXCMPNT.Component_Version
    FROM
        CAXVSMD
      , CAXVM
      , CAXAGENT
      , CAXCMPNT
      , CAXVMD
      , CAXINTVL
    WHERE
          Int_start_date BETWEEN TO_CHAR(SYSDATE-7, 'YY/MM/DD') AND TO_CHAR(SYSDATE, 'YY/MM/DD')
      AND CAXVMD.VMS = CAXVSMD.VMS
      AND CAXVMD.INTVL = CAXVSMD.INTVL
      AND CAXVSMD.VMS=CAXVM.INDEXX
      AND CAXVSMD.AGENTS=CAXAGENT.INDEXX
      AND CAXVSMD.CMPNTS=CAXCMPNT.INDEXX
      AND CAXVMD.VMS=CAXVM.INDEXX
    GROUP BY
         CAXINTVL.Int_start_date
      , CAXVM.Virtual_Type
      , CAXVM.Partition_Name
      , CAXVM.Operating_System_Name
      , CAXVM.Operating_System_Version
      , CAXAGENT.Collector_Name
      , CAXAGENT.Collector_Build_Date
      , CAXAGENT.Collector_Version
      , CAXCMPNT.Component_Name
      , CAXCMPNT.Component_Build_Date
      , CAXCMPNT.Component_Version
    ORDER BY
        CAXINTVL.Int_start_date
      , CAXVM.Partition_Name
    ;

        

    Via the BPAMaintenanceTool.sh command run locally on each agent

        

    In Perform version 7.5.00 and later the patch installation is handled by the BPA Maintenance Tool java based patch installation utility. So connect to a system of interest and

        

    On Unix

        
    From the Command Line
    Run the following command:   
         
          > $BEST1_HOME/BPAPatchTool.sh -list   
        
    Output will look something like this:   
         
        > $BEST1_HOME/BPAPatchTool.sh -list    
    /usr/adm/best1_7.5.00/./PatchInstaller.jar    
    /usr/adm/best1_7.5.00/../../../BMCBPAInstallJVM/bin/java    
    /usr/adm/best1_7.5.00    
    verbose mode on    
    Parsed command line arguments    
    patch - Mon Mar 22 15:03:29 EDT 2010 -- bpa_console_solaris_7.5.00_patch_06    
    patch - Mon Mar 22 15:00:53 EDT 2010 -- bpa_agent_solaris_7.5.00_patch_03    
    patch - Fri Jan 08 11:32:19 EST 2010 -- bpa_console_solaris_7.5.00_patch_02    
    patch - Tue Dec 29 09:36:52 EST 2009 -- bpa_console_solaris_7.5.00_patch_01   
        
    In that example the latest console patch set installed on the machine is 'bpa_console_solaris_7.5.00_patch_06' and the latest agent patch set installed on the machine is 'bpa_agent_solaris_7.5.00_patch_03'.   
         
        NOTE: If the $BEST1_HOME/BPAPatchTool.sh does not exist that may mean that no patches have been applied to this console (since the first patch installation creates the BPAPatchTool.sh command). You can verify this using the BPAMaintenanceTool.cmd tool described below.    
        
    Alternately, you can run the BPAMaintenanceTool.cmd to determine the patch level:    
          > [Perform Installation Directory]/BPAMaintenanceTool.sh -list   
        
    For example, this command:   
         
          > $BEST1_HOME/../../../BPAMaintenanceTool.sh -list   
         

    On Windows

    Run the following command:   
         
          > "%BEST1_COLLECT_HOME%\..\..\BPAMaintenanceTool.cmd" -list   
        
    Output will look something like this:   
         
        C:\Program Files\BMC Software\Patrol3>"%BEST1_COLLECT_HOME%\..\..\BPAMaintenanceTool.cmd" -list    
    Using - C:\Program Files\BMC Software\Patrol3\BMCBPAInstallJVM\bin\java.exe    
    Using - .\PatchInstaller.jar    
    verbose mode on    
    Parsed command line arguments    
    patch - Mon Mar 22 15:25:13 EDT 2010 -- bpa_console_windows_7.5.00_patch_06    
    patch - Mon Mar 22 15:22:20 EDT 2010 -- bpa_agent_windows_7.5.00_patch_03    
        
       
       

    Section III: Perform version 7.4.10 and earlier

       
        

    On Unix

    Check the contents of the $BEST1_HOME/local/setup/patch_uninstall.csv file.   
      
    Check the first field (before the comma) of the last line in the $BEST1_HOME/local/setup/patch_uninstall.csv file on the machine that includes the word 'agent' (for the latest agent patch) or 'console' (for the latest console patch). That will give you the latest version of the patch set installed on that agent machine.   
      
    So, if the last line looks like this:   
    pp_7.3.00_agent_patch_Solaris.013,bgscollect,/usr/adm/best1_7.3.00/...   
      
    That would mean Perform version 7.3.00 agent patch set #013 is installed on the machine.   
      
    This command should give you one line that tells the last agent patch version installed:   
         
    For the console
        
          > grep console $BEST1_HOME/local/setup/patch_uninstall.csv | awk -F, '{ print $1 }' | tail -1   
         
    For the agent
        
          > grep agent $BEST1_HOME/local/setup/patch_uninstall.csv | awk -F, '{ print $1 }' | tail -1   
        
    You would then need to compare that with the latest patch set available on the BMC FTP site.   
      
    If the patch_uninstall.csv file does not exist then that means that either:   
         
         
    • no Perform patch packages have been applied to this machine (most likely) or
    •   
        
         
    • Perform patches have been applied using a method other than the install_patch script, such as the Common Installer or the BMC Performance Manager Distribution Server.
    •   
        

    On Windows

    Check the contents of the %BEST1_COLLECT_HOME%\local\setup\patch_uninstall.csv file where %BEST1_COLLECT_HOME% is, by default, "C:\Program Files\BMC Software\Patrol3\Best1\V.V.VV" where V.V.VV is the product version number such as '7.4.00'.   
      
    Check the first field (before the comma) of the last line in the %BEST1_COLLECT_HOME%\local\setup\patch_uninstall.csv file on the machine that includes the word 'agent' (for the latest agent patch) or 'console' (for the latest console patch). That will give you the latest version of the patch set installed on that agent machine.   
      
    If the patch_uninstall.csv file does not exist then that means that either:    
         
    • no Perform patch packages have been applied to this machine (most likely) or
    •    
    • Perform patches have been applied using a method other than the install_patch script, such as the Common Installer or the BMC Performance Manager Distribution Server.
    •   
       
      
      

    Is this information available from VMware guests?

      

    A related topic is that how to get Perform agent version information for a collector that has been installed on VMware guest machine (usually this would be either a Windows or Linux collector).  This type of system is referred to as a "VIRTUAL" node, and that classification is further described in 000030949: Exactly what is a VIRTUAL node in Performance Assurance and Capacity Optimization integration with BPA (BCO-EE)? (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000030949)

      

    Currently, it is not possible to get the VMware guest Perform agent version details from anywhere except the machine running the data collection because that information is not stored in database. Currently there is no way to map Virtual Nodes (VMware guests running local collectors)  to the collector version information in the CAXCMPNT table.  The reason is that Virtual Nodes aren't stored anywhere in the new database schema (7.5.00 and higher) -- they are only reported in the CAXNODE table and there isn't a mapping between the CAXNODE table and the CAXCMPNT table.

    At this time there is an RFE to enhance the Visualizer database schema to include a mapping between the CAXNODE table and the CAXCMPNT table. That RFE has not yet been scheduled for implementation in a particular release.  However it is possible to get the information using PrintUDR command. Please contact Technical Support if you would like to use this method.

      

    These are the details for the Request for Enhancement (RFE) QM001764416: 'Request to have agent version information populated to database for VMware guest machines Perform agent installed on them'.

      

     

      
    Related Products:  
       
    1. TrueSight Capacity Optimization
    2.  
    3. BMC Performance Assurance for Servers
    4.  
    5. BMC Performance Analyzer for Servers
    6.  
    7. BMC Performance Analysis for Servers

     


    Article Number:

    000205898


    Article Type:

    FAQ/Procedural



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