Upgrading the Gateway Server silently

Where you are in the Upgrade process

The silent upgrade process involves running the installer from a command line. The installer uses the ConsoleSilentInstallOptions.txt file that contains the parameters to be configured while upgrading the Gateway Server.

To upgrade the Gateway Server silently

1. Log in to the computer where you want to upgrade the Gateway Server.
   
   • (Windows) Log in as a user with administrator privileges.
   • (Linux) Log in as a non-root user.
2. Extract the Gateway Server installer files to a temporary directory. 
   
   • (Windows) Extract TSCO_GatewayServer_<version>_MSwindows.zip
   • (Linux) Run this command: tar -xvf TSCO_GatewayServer_<version>_Linux.tar
3. Create a directory for saving the options file.
4. In the directory where you extracted the Gateway Server installation files, navigate to the silent directory. 
5. Copy the ConsoleSilentInstallOptions.txt file from this directory to the directory that you created in Step 3.

6. Open the ConsoleSilentInstallOptions.txt file in a text editor and configure the following parameters:

   Parameter	Description
   (Linux) -J PERFORM_UNIX_MIGRATION	Specify whether you want to migrate the existing Manager runs that are scheduled. The default value is True.
   (Linux) -J PERFORM_UNIX_MIGRATE_AGENT_LIST	Specify whether you want to migrate the agent list to use the latest Gateway Server being installed. The default value is True.
   (Linux) -J PERFORM_UNIX_UNINSTALL	Specify whether you want to uninstall the existing version of the Gateway Server if detected. The default value is False. Warning If you want to migrate the existing Manager runs, do not uninstall the existing Gateway Server.
   (Windows) -J PERFORM_CONSOLE_MIGRATION	Specify whether you want to migrate the existing Manager runs that are scheduled. The default value is True.

   You can retain the default values for the other parameters. For information about the other parameters, see 2020-02-18_12-36-03_Installing the Gateway Server silently. 

7. Change to the directory that contains the Gateway Server installation files that you extracted.

8. Run the following command:

   • (Windows)
     start /WAIT setup.exe -i silent-DOPTIONS_FILE="<driveName>:\<fileLocationPath>\ConsoleSilentInstallOptions.txt"
   • (Linux)
     ./setup.sh -i silent -DOPTIONS_FILE=<fileLocationPath>/ConsoleSilentInstallOptions.txt

   The variables <driveName> and <fileLocationPath> represent the location where you saved the options file. If the path contains spaces, enclose the path and options file name in quotation marks.
   A confirmation message about the successful installation is displayed.

9. (Linux) Run the following command as a root user to configure the embedded Capacity Agent:

   1. Change to the root user.
   2. Change to the installation directory. The default is /opt/bmc/Patrol3.
   3. Run the following command:
      ./b1config<version>.sh

   where version indicates the version of the installed Gateway Server.

10. Verify that the upgrade is successful:
    
    • Verification steps for Windows:

      To verify the upgrade of the embedded Capacity Agent

      1. On the computer where the Gateway Server is installed, click Start > Settings > Control Panel.
      2. Double-click PATROL - Perform Agent.
      3. Verify that the status of the BGS_SDService service daemon is Running.

      To verify the environment variables

      1. Open the command prompt, and run the following command:
         echo %best1_home%
      2. Ensure that the following installation location is displayed:
         C:\Program Files\BMC Software\Patrol3\BEST1\NTC

      To verify data collection

      To verify that the Gateway Server collects data from the embedded Capacity Agent and the Agents that are installed on other computers, do the following:

      1. Click Start > All Programs > BMC Software > Gateway Server > Collect Data.
      2. Click Start a collect process on a Console or Agent computer, and click Next.
      3. Select one of the following collection modes, and click Next.
         
         • Standard Mode: Transfers the collected data across a network from the target computers to the Gateway Server.
         • Secure Mode: Transfers the collected data locally.

      1. • Collect from a policy file: Transfers data from the computer names that are defined in a text file.

      1. If you selected Collect from a policy file, select the policy file, and click Next. You are directed to Step f.
      2. Specify one the following options to add the computers from which you want to collect data, and click Next.
         • Agent computers or network address: Type the names (host names or fully qualified domain names) or IP addresses of the computers on which you have installed Capacity Agents. Separate names with a comma (,). If this field is left blank, data collection starts from the embedded Capacity Agent.

      1. • Optional name of Agent computer: Type the name of computer where the agent is installed. If the computer has identification other than its network name, type that name. For example, a computer with the network name 1on_subnet5 might be a mail server with an internal name emailC. The specified name appears as a directory name where the collected data is stored. For example, C:\Program Files\BMC Software\BEST1\NTC\History\emailC. The specified name appears as a directory name where the collected data is stored. For example, C:\Program Files\BMC Software\BEST1\NTC\History\emailC.
           If this field is left blank, the folder name in the collection repository takes the network name. For example, C:\Program Files\BMC Software\BEST1\NTC\History\1on_subnet5.
         • File with list of computers to collect: Specify the text file that contains the agent computer names from which you want to collect data.

      1. Type the path of the data collection directory on the agent and Gateway Server computers, and click Next.
         • Repository on the Console: Select the path to the data collection directory on the computer where the Gateway Server is installed.
         • Repository on the Agent: Select the path to the temporary repository on the computer where the agent is installed.
         • Select the action that must start after the data collection wizard is exited.

      1. Select the frequency for collecting and summarizing data, and click Next.
         
         • Collect data every: Specify the frequency at which the data collector must place the collected data in the memory. The default value is 10 seconds.

      1. • Summarize data every: Select the interval, in minutes, at which the Capacity Agent summarizes data and saves it in the repository.
      2. Specify one of the following data collection schedules, and click Next.
         
         • Begin immediately: Begins collection immediately after existing the wizard and stops after 24 hours.

      1. • Begin: Begins collection after the specified time and ends after the specified duration.

      1. • Begin and end by date and time: Starts and ends collection on the specified dates and at the specified times.
      2. Review the settings and click Finish.
      3. When the collection duration ends, confirm that the correct files are created and transferred from the agent computers to the Gateway Server computer in the following formats:
         
         • repository\computerName\date.time\type-of-stats\raw.udr
         • repository\computerName\date.time\type-of-stats\raw.lox
           (The default repository on the Gateway Server computer is C:\Program Files\BMC Software\Patrol3\NTC\history).

           Warning

           The temporary default repository on the agent computer is C:\Program Files\BMC Software\Patrol3\BEST1version\History. This directory serves as a repository until the data is transferred to the Gateway Server computer.
    • Verification steps for Linux:

      To verify that the GatewayManagerServer process is running

      1. Run this command to verify that port 10129 is enabled on the Gateway Server:
         netstat -an |grep 10129
      2. Run this command to verify that the General Manager service is running:
         telnet <GW_server_hostname> 10129
      3. Run this command to verify that the GeneralManagerServer process is up and running:
         ps -ef |grep GeneralManagerServer

      To verify data collection

      1. To configure the BEST1_HOME environment variable, run the following commands:

      1. 1. Change to the non-root user.
         2. Run the following commands:
            
            • For the Korn or Bourne shell:
              
              1. BEST1_HOME=usr/adm/best1_<version>
              2. export BEST1_HOME
            • For the C shell:
              setenv BEST1_HOME usr/adm/best1_<version>
              where version indicates the version of the installed product component.
      2. To test the connection to the Agent, run the following command:
         $BEST1_HOME/bgs/scripts/best1collect -n <targetHostName> -q
         The following example shows the result of running this command on the clm-pun-015565 system:

         [perform@clm-pun-032515 ~]$ $BEST1_HOME/bgs/scripts/best1collect -n clm-pun-015565 -q best1collect on clm-pun-032515: requesting Update Status on clm-pun-032515 ... Wed Mar 15 00:06:00 2017 Agent Query Request Starting(/usr/adm/best1_10.7.00/bgs/monitor/log/clm-pun-032515-bgsagent_6767.als) Collect Instance Node Started Started Name Name Name By On ------------ -------------- ---------- ---------- ----------------- ------------ -------------- ---------- ---------- ----------------- *Node: clm-pun-032515 has acknowledged Query request successfully.
         
      3. To initiate a data collection request, run the following command. Replace <nodeName> with the name of the system where you want to initiate the collection request.
         $BEST1_HOME/bgs/scripts/best1collect -n <nodeName> -e +15 -d /tmp -w 1

         The following example shows the result of running this command on the clm-pun-015565 system:

         [perform@clm-pun-032515 scripts]$ $BEST1_HOME/bgs/scripts/best1collect -n clm-pun-015565 -e +15 -d /tmp -w 1 best1collect on clm-pun-032515: requesting Start Collect on clm-pun-015565 ... best1collect requesting bgscollect start on clm-pun-015565... Tue Mar 14 22:30:04 2017 best1collect: Collect process with instance noInstance will be started on node clm-pun-015565. Specified data repository: /tmp. *Node: clm-pun-015565 has acknowledged Start request successfully.
         
      4. To verify the status of data collection, run the following command:

         $BEST1_HOME/bgs/scripts/best1collect -n <nodeName> -Q

         The following example shows the result of running this command on the clm-pun-015565.bmc.com system:

         [perform@clm-pun-032515 scripts]$ $BEST1_HOME/bgs/scripts/best1collect -n clm-pun-015565.bmc.com -Q best1collect on clm-pun-032515: requesting Update Status on clm-pun-015565.bmc.com ... Tue Mar 14 22:35:50 2017 Agent Query Request Starting(/usr/adm/best1_10.7.00/bgs/monitor/log/clm-pun-015565-bgsagent_6767.als) Collect Instance Node Started Started Data Length Spill SampleState Config Active Active Term Term LagTime Name Name Name By On Repository HH:MM (Min) (Sec) Groups Data No Data Data No Data (Min) ------------ -------------- ---------- --------------------------- ----------------------------- ------ ----- ------------------------ ------ ------ ------- ---- ------- ------- SYSTEM noInstance clm-pun-015565 perform Mar-14-2017.22.30/tmp 0:15 15 10 UDR_WRITE_ACTIVE 46 19 2 0 25 0 ------------ -------------- ---------- --------------------------- ----------------------------- ------ ----- ------------------------ ------ ------ ------- ---- ------- ------- *Node: clm-pun-015565.bmc.com has acknowledged Query request successfully.
         
      5. Verify that the Active Data parameter shows a value greater than 0, which indicates that the data collector is functioning as expected.

Next step in the Upgrade process

Now that you have successfully upgraded the Gateway Server, upgrade the Capacity Agent to collect data at a greater granularity. Else, complete the post-upgrade activities.