Upgrading the Gateway Server using the wizard

Where you are in the Upgrade process

When you plan to upgrade from a version of the Gateway Server that is prior to the last two releases, you must upgrade to at least one interim upgrade before directly upgrading to the current version. The embedded Capacity Agent, which includes the system collectors and service daemon, is automatically upgraded with the Gateway Server. 

When you upgrade the Gateway Server, the installation wizard follows the path of the initial installation. For example, if the typical installation type was used during installation, the same type is selected during the upgrade process. Also, the custom parameters that were configured during installation are retained. You cannot change the installation directory of Gateway Server. Therefore, this option is not displayed during the upgrade process.

To upgrade the Gateway Server

  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. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:
    export DISPLAY=<IP address of the computer>:0.0
  1. Run the installer:
    • (Windows) Run setup.exe from the windows_gateway_server directory.
    • (Linux) Run setup.sh from the linux_x86_console directory.
  2. Review the welcome page, and click Next.
  3. Read the license agreement, agree to the terms, and click Next.
  4. Ensure that the Gateway Server component is selected for installation, and click Next.
  5. Verify the installation type.
    • If the installation type is typical, verify or modify the following settings on the subsequent screens, and click Next.
      1. The protocol to be used for communication
      2. If you selected HTTPS in the previous step, specify the following details of the Application Server to retrieve its server certificate:
        • The host name and the port number
        • The administrator user name and password
      3. The network protocol to be used
    • If the installation type is custom, verify or modify the following settings on the subsequent screens, and click Next.
      1. The protocol to be used for communication
      2. If you selected HTTPS in the previous step, specify the following details of Application Server to retrieve its server certificate:
        • The host name and the port number
        • The administrator user name and password
      3. The security level for the communication between the Gateway Server and the Agent
      4. (Linux) The name of the user who will access and use the Gateway Server
      5. The port numbers and data collection options:
        • Port numbers for the service daemon, Capacity Agent, status reporting, and Gateway Server
        • History Data Repository: The directory path to save the historical data.
        • (Linux) Collect Data Repository: The directory path to save the collected data temporarily.
        • (Linux) Service Daemon installation directory: The directory path where the service daemon is installed.
        • Enable collection of historical data: Specify whether you want to collect historical data. By default, the historical data collection is enabled.
        • Set TrueSight Capacity Optimization Agent to start automatically: Specify whether you want to start the Capacity Agent immediately after installation. By default, the Agent does not start after installation.
        • (Linux) Create Default Link: Specify whether you want to create the usr/adm/best1_default link to identify the current installation. By default, the link is created.
        • Maximum process command length to collect: Select the maximum length (in bytes) of the process command that the Capacity Agent must collect. The default value is 2048.
        • (Linux) Specify whether you want to run the service daemon (bgssd.exe) in the standalone mode. By default, the service daemon is configured to run by using the inetd or xinetd service.

      2. The migration options:
        (Windows)

        • Migrate Agent: Select if you want to migrate the agent data files during the upgrade, such as agent.cfg and authorization.cfg. For more information about these files, see Agent-configuration-file and Authorization configuration file.
        • Migrate Gateway Server: Select if you want to migrate the Gateway Server files during the upgrade, such as policy files (.plc), script files (.vmn and .msf), the settings file (perform.msc), the hardware table files (best1user.odm and best1user.hrw), the license file, scheduled scripts, and the configuration files that are available in the \BEST1\NTC\local\setup directory (The default path is C:\Program Files\BMC Software\Patrol3\\BEST1\NTC\local\setup).

        • Uninstall existing version: Select to remove the current version of Gateway Server before upgrading it.

          If you want to migrate the scheduled Manager runs, do not select uninstalling the existing version of Gateway Server.

        (Linux)

        • Migrate configuration files: Select if you want to migrate the agent configuration files that are available in the following directory: $BEST1_HOME/local/setup
        • Migrate agent list and gateway manager runs: Select to migrate the scheduled Manager runs from the previous version of the Gateway Server that includes Manager runs automatically created using agent lists. When the Gateway Server is upgraded to the new version, the Manager runs will be unscheduled in the previous version and the new Manager runs will be scheduled in the new version.

        • Uninstall existing version: Select to remove the current version of Gateway Server before upgrading it.

          If you want to migrate the scheduled Manager runs, do not select uninstalling the existing version of Gateway Server.

        • The PATROL agent configuration
          If the PATROL agent is installed in your environment, specify whether you want this agent to use the data collectors of the upgraded Gateway Server.

      3. The IPv4 or IPv6 network protocol to be used
  2. Review the installation summary and click Install.
    A message confirming the completion of installation process is displayed.
  3. Click View log to view the installation log details on the screen.
  4. Click Done to exit the installation program.

  5. (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.

  6. 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.
        • 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.
        • 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.
        • 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.
        • Begin: Begins collection after the specified time and ends after the specified duration.
        • 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).

          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. 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.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*