When changing the hostname of the TrueSight Capacity Optimization(TSCO) Gateway Server console, what steps are necessary to ensure a seamless transition within Manager?

Version 6
    Share This:

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


    PRODUCT:

    BMC Performance Assurance for Servers


    APPLIES TO:

    TrueSight Capacity Optimization (Gateway Server) 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0 ; BMC Performance Assurance 9.5



    QUESTION:

     
       There are a few areas of the TrueSight Capacity Optimization (TSCO ) Gateway Server product that use the hostname of the console as an access control key or as component of a file name that is used to maintain persistent information on the console. What is the best way to handle the hostname of the console being changed on the Perform console?   
         
         
         NOTE: For information on how to handle a console IP address change without a hostname change see KA       000031272: 'Does anything need to be done if the IP address of the TSCO Gateway Server console is changed? Will that impact the scheduled Manager runs?'   
         
              
        
       
       
        
         
    • TrueSight Capacity Optimization (Gateway Server) 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0
    •    
    • BMC Performance Assurance 9.5
    •   
       
       
        
         
    • Perform console
    •   
       


    ANSWER:

     

       

    Section I: Unix Console

       
       There are three areas of the product that rely on the hostname of the console on Unix:    
         
    • UDR Collection Manager
    •    
    • Investigate
    •    
    • Pcron
    •   
         UDR Collection Manager (UCM)   
      
    UDR Collection Manager (UCM) maintains a list of active Manager runs and the status of data collection on the remote nodes in the [hostname].MRQ file. If the hostname of the machine is changed UCM will be unable to locate this file which will result in both data transfer and data processing failing on the day the hostname of the console is changed. Future Manager runs would continue to work properly after the hostname change over.   
      
    To ensure seamless UCM data handling after the hostname change do the following:   
      
       Step 1  
      
    Copy the $BEST1_HOME/local/manager/run/[hostname].MRQ file to $BEST1_HOME/local/manager/run/[new_hostname].MRQ right before you change the hostname.   
      
       Step 2    
            
    Change the hostname   
      
       Step 3  
      
    Reboot   
      
       Step 4    
            
    After the reboot, wait until after the first collector restart query and then check to see if the new udrCollectMgr processes have started and are running. If they are running, wait another 15 minutes or so and then check the UCM Status Reports to see that they are being properly updated.   
      
    Copying the [hostname].MRQ to [new_hostname].MRQ is enough for a seamless transition from the original hostname to the new hostname for UDR Collection Manager.   
      
       Pcron  
      
    On Linux, the Manager 'pcron' job is scheduled in 'cron' to execute every minute and when appropriate execute scheduled runs of the Manager related scripts such as the *.Collect, *.XferData, and *.Manager scripts. The hostname of the machine is part of the files that pcron references to know which scripts to execute.   
      
    To ensure seamless pcron script execution after the hostname change do the following:   
      
       Step 1  
      
    Copy (or rename) the $BEST1_HOME/bgs/pcron/repository/[hostname]-[user].pcron and [hostname]-[user].counter files to [new_hostname]-[user].pcron and [new_hostname]-[user].counter respectively.   
      
       Step 2  
      
    Change the hostname   
      
    Step 3   
      
    Reboot   
      
    Step 4   
      
    After the reboot, wait until after the first collector restart query and then check to see if the new udrCollectMgr processes have started and are running. If they are running that means that 'pcron' is being properly executed.   
      
    One could also check the $BEST1_HOME/bgs/log/pcron/[new_hostname].log file to see that it is being created.   
      
       Investigate

    NOTE
    : This section describes deprecated functionality of Investigate that does not exist in the new TrueSight Presentation Server (TSPS) webInvestigate tool.   
      
    Investigate uses the hostname of the TSCO Gateway Server console as part of the 'Access Control' list for alerts on the remote node. That means that if the hostname of the console is changed it is possible that users will no longer be able to deactive those alerts.   
      
    When changing the hostname of the console it would be best to stop and active Investigate alerts and then re-active them after the hostname has been changed. The access control for the alert is done via two fields the 'CONSOLE_NAME' field (which is the IP address of the console) and the 'ACCESS_CONTROL' field which is username@hostname. If the hostname changes the 'new' console won't match the ACCESS_CONTROL string and the clear request will be rejected.   
       
       

    Section II: Windows Console

       
       There are two areas of the product that rely on the hostname of the console on Windows:    
         
    • UDR Collection Manager
    •    
    • Investigate
    •   
          UDR Collection Manager (UCM)  
      
    UDR Collection Manager (UCM) maintains a list of active Manager runs and the status of data collection on the remote nodes in the [hostname].MRQ file. If the hostname of the machine is changed UCM will be unable to locate this file which will result in both data transfer and data processing failing on the day the hostname of the console is changed. Future Manager runs would continue to work properly after the hostname change over.   
      
    To ensure seamless UCM data handling after the hostname change do the following:   
      
       Step 1  
      
    Copy the %BEST1_HOME%\local\manager\run\[hostname].MRQ file to %BEST1_HOME%\local\manager\run\[new_hostname].MRQ right before you change the hostname.   
      
    Step 2   
      
    Change the hostname   
      
       Step 3  
      
    Reboot   
      
       Step 4  
      
    After the reboot wait 15 - 20 minutes and then check the UCM Status Reports to see that they are being properly updated. On Windows the UCM functionality is built into the best1man.exe process.   
      
    Copying the [hostname].MRQ to [new_hostname].MRQ is enough for a seamless transition from the original hostname to the new hostname for UDR Collection Manager functionality.   
      
       Investigate  
      
       NOTE: This section describes deprecated functionality of Investigate that does not exist in the new TrueSight Presentation Server (TSPS) webInvestigate tool.   
      
    Investigate uses the hostname of the Perform console as part of the 'Access Control' list for alerts on the remote node. That means that if the hostname of the console is changed it is possible that users will no longer be able to deactive those alerts.   
      
    When changing the hostname of the console it would be best to stop and active Investigate alerts and then re-active them after the hostname has been changed. The access control for the alert is done via two fields the 'CONSOLE_NAME' field (which is the IP address of the console) and the 'ACCESS_CONTROL' field which is username@hostname. If the hostname changes the 'new' console won't match the ACCESS_CONTROL string and the clear request will be rejected.   
       
       

    Additional Information

    The hostname of the Perform console is not used as part of data transfer and except for access control lists it is not important for successful data collection or data transfer in relation to the remote node itself. All network communication initiated by the remote node to the console is done via the IP address of the Perform console - not via the hostname. 
      
        
      
    Related Products:  
       
    1. TrueSight Capacity Optimization
    2.  
    3. BMC Performance Assurance
       Legacy ID:KA291362

     


    Article Number:

    000238094


    Article Type:

    FAQ/Procedural



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