Upgrading a PXE server on Linux or UNIX

This topic provides instructions for using the component-level installer to upgrade a PXE server in the following scenarios:

  • On a Linux or UNIX computer where the PXE server was not installed as part of the Application Server installation
  • On a Linux or UNIX computer where the PXE server is installed as part of the Application Server installation (in this case, an upgrade of the Application Server also upgrades the PXE server.)

To upgrade the PXE server as part of a complete environment upgrade, see Upgrading-on-Linux-using-the-unified-product-installer.

This topic includes the following sections:

Warning

If the PXE server is installed on a computer where the TrueSight Server Automation Console is also installed, you should perform this task only after upgrading all other components in a TrueSight Server Automation system.

Before you begin

  • To perform the upgrade of the PXE server, you must have root privileges.
  • If the PXE server is installed on an operating system that differs from the operating system on the Application Server where you run the installation, you cannot use the unified product installer to upgrade the PXE server. However, you can use the unified product installer to upgrade the other product components, and can then run the PXE server component installer (as described on the current page). In such a scenario, perform the following steps before you begin the PXE server upgrade:
    1. Stop the PXE server / TFTP server.
    2. Run the unified product installer. The installer ignores the PXE server, as it is in a stopped state.
      The installer upgrades the rest of the infrastructure, with the exception of the PXE server.
  • All configuration data in TrueSight Server Automation must be copied to the database. This step is performed automatically by the unified product installer. If you use the individual component installers for upgrade, you must run the configurator on all PXE servers in your TrueSight Server Automation environment before you upgrade the servers using the individual component installers. See Migrating-the-database-and-persisting-configuration-data-to-the-database.
  • Ensure that NSH is installed on the Linux or UNIX PXE server. 

To upgrade a standalone PXE Server on Linux or UNIX

  1. Log on as root.
  2. Record the following settings for the PXE server:
    • Database connectivity information
      The PXE server uses the same database as the Application Server. One way to obtain this information is to start the Application Server Administration Console (also known as the blasadmin utility) and enter the following command:
      show database all
    • Host name and IP address of the PXE server
    • DHCP server location (local or remote)
    • TFTP root directory
      You do not have to record the name and location of the data store.
    • If you are using the Multi-Database mode, make a note of the additional database configuration parameters found in the <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml file.
  3. Make a backup copy of configuration files.
    If you are using the pxe.conf configuration override file, make a copy of the <install directory>/NSH/br/pxe.conf file.
  4. Navigate to the directory that contains upgrade files and run the upgrade script for TrueSight Server Automation. (Script names follow the convention: BBSA<version>-<platform>.)
  5. Enter y to continue.
    A message prompts you to choose a language for the installation program.
  6. Enter the number corresponding to the language that you want to use.
  7. Enter y to continue.
    Licensing text is displayed.
  8. Enter y to agree to the terms and continue.
    A list displays the TrueSight Server Automation components to be upgraded and prompts you to continue.
  9. Enter y.
    A series of messages is displayed, and then the upgrade script is complete.
  10. Copy the backup of the pxe-data-sources.xml file into <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml.
  11. Merge the configurations of the <install directory>/NSH/br/pxe.conf and the backed up copy.
  12. During the upgrade process, the PXE server global.properties file is overwritten. Copy the global.properties file on the Application Server to the br/deployments directory on the PXE machine.
  13. (Optional) If you want to enable security for RMI interfaces by using SSL to encrypt connections, set the values of UseSSLSockets and RequireClientAuthentication Application Server parameters to true as shown here. Then, copy the bladelogic.keystore file from the <installationDirectory>\br\deployments directory of the central Application Server to the br\deployments directory on the PXE server.
  14. Restart the PXE server. See Starting-and-stopping-a-PXE-server.

Troubleshooting Tip

If you start the PXE server without copying the global.properties file to the PXE machine, and try to start the PXE service, the PXE service does not start.

To troubleshoot this situation:

  1. Copy the the global.properties file as described in step 12, above.
  2. Delete the _pxe  folder created during the unsuccessful start from the br/deployments directory on the PXE machine.

To upgrade a combined PXE and Application Server on Linux or UNIX

  1. Log on as root.
  2. Record the following settings for the PXE server:
    • Database connectivity information
      The PXE server uses the same database as the Application Server. One way to obtain this information is to start the Application Server Administration Console (also known as the blasadmin utility) and enter the following command:
      show database all
    • Host name and IP address of the PXE server
    • DHCP server location (local or remote)
    • TFTP root directory
      You do not have to record the name and location of the data store.
    • If you are using the Multi-Database mode, make a note of the additional database configuration parameters found in the <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml file.
  3. Make a backup copy of configuration files.
    If you are using the pxe.conf configuration override file, make a copy of the <install directory>/NSH/br/pxe.conf file.
  4. Follow the Application Server upgrade steps.
  5. Copy the backup of the pxe-data-sources.xml file into <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml.
  6. Merge the configurations of the <install directory>/NSH/br/pxe.conf and the backed up copy.

Where to go from here

Upgrade the other TrueSight Server Automation Application Servers, consoles, RSCD agents, and other components in your enterprise (including on any file servers or virtual servers).  See:

Upgrading-the-Network-Shell-on-Linux-and-UNIX

Upgrading-the-Network-Shell-on-Windows

Upgrading-the-RSCD-agent-on-Linux-and-UNIX

Upgrading-the-RSCD-agent-on-Windows

Upgrading-the-file-server.

Note

If the TrueSight Server Automation file server resides on a different computer from the Application Server, upgrade the RSCD agent on the computer on which file server resides. The file server and the database must be at the same version before you run TrueSight Server Automation.


 

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