Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This section presents procedures and guidelines to change the configuration of your deployment environment:

Even with the best of planning, your monitoring environment can change and you might need to change the deployment configuration of the servers.

Warning

Changes to your deployment might result in data gaps because monitoring solutions can momentarily lose their configuration data while the changes are taking place.

For detailed installation instructions, see BMC ProactiveNet Installation and Configuration Guide.

Changing from a single-server deployment to a multiple-server deployment

BMC recommends that you plan for a multiple-server deployment unless you are absolutely sure that you will not need a larger environment in the future. With a multiple-server deployment, you can more easily add BMC ProactiveNet Child Servers as the number of managed devices and metrics grows.

Changing to a multiple-server environment early in the deployment cycle

You can change from a single-server deployment to a multiple-server deployment early in the deployment cycle, before a large amount of data is collected. In this scenario, you can enable Central Monitoring Administration on the original server, Server 1, and then add a child server.

  1. If Central Monitoring Administration is not enabled on the original server, Server 1, follow the steps to enable it, including downloading and installing the Central Monitoring Repository.
    Server 1 is now the BMC ProactiveNet Central Server and no additional monitoring should be configured from it.
  2. Install a new BMC ProactiveNet Child Server, Server 2, and enter Server 1 as the BMC ProactiveNet Central Server when prompted during the installation process.
  3. Use Server 2 for additional monitoring needs.

Changing to a multiple-server environment after the server reaches maximum capacity

You can change from a single-server deployment to a multiple-server deployment after monitoring reaches maximum capacity (see sizing guidelines at Performance and scalability recommendations). In this scenario, you add a new BMC ProactiveNet Central Server, Server 2, with Central Monitoring Administration, and the original server, Server 1 becomes a child server.

  1. Install a new BMC ProactiveNet Server, Server 2, enable Central Monitoring Administration, and install the Central Monitoring Repository.
    This server is the BMC ProactiveNet Central Server
  2. Apply the license on the new BMC ProactiveNet Central Server.
  3. Manually recreate all the policies which were on the original server, Server 1, on the new BMC ProactiveNet Central Server.
  4. Disable Central Monitoring Administration Server 1:
    1. In the <installationDirectory>/pw/custom/conf/pronet.conf file on Server 1, set the bppm.centraladmin.enabled property to false.
    2. Restart Server 1 by running the pw system start command.
      The Central Monitoring Repository and other Central Monitoring Administration artifacts remain on Server 1, but they are no longer relevant.
  5. Register Server 1 as a BMC ProactiveNet Child Server to Server 2.

    Warning

    Ensure that policies are recreated on the new BMC ProactiveNet Central Server before you register the child server. Otherwise, the configuration on the agents could get blanked out.

  6. As required, you can add more BMC ProactiveNet Child Servers to the BMC ProactiveNet Central Server (Server 2).

Changing a BMC ProactiveNet Central Server to a BMC ProactiveNet Child Server

Warning

BMC does not recommend or support the changing of a BMC ProactiveNet Central Server to a BMC ProactiveNet Child Server.

BMC recommends adding a new child server to the environment instead of trying to change a Central Server.

Connecting a BMC ProactiveNet Child Server to a different BMC ProactiveNet Central Server

Warning

BMC does not recommend connecting a BMC ProactiveNet Child Server to a different Central Server unless absolutely required. The procedure might result in data gaps.

  1. Install a new BMC ProactiveNet Server, Server 2, enable Central Monitoring Administration, and install the Central Monitoring Repository.
  2. Ensure that the Central Monitoring Repository on the new Central Server, Server 2, is identical to that on the original Central Server, Server 2.
    If necessary, apply updates to the repositories to ensure that they are identical.
  3. Manually recreate all the policies which were on the original Central Server, Server 1, on the new BMC ProactiveNet Central Server.
  4. Deregister the BMC ProactiveNet Child Server from BMC ProactiveNet Central Server, Server 1, by using the pw cmadmin deregisterChildServercommand:

    pw cmadmin deregisterChildServer -cmaHost=<cmaHost> [-cmaPort=<cmaPort>]
    -cmaUser=<cmaUser> -cmaPasswd=<cmaPassword> [-cmaProtocol=http|https]
    

    For details about the command, see the BMC ProactiveNet Command Line Interface Reference Guide.

  5. Register the BMC ProactiveNet Child Server to Server 2.

    Warning

    Ensure that policies are recreated on the new BMC ProactiveNet Central Server before you register the child server. Otherwise, the configuration on the agents could get blanked out.

Monitoring from the BMC ProactiveNet Central Server

Note

BMC does not recommend adding monitoring to the BMC ProactiveNet Central Server, except for the Self-Monitoring Service that is installed automatically, for the following reasons:

  • Additional monitoring can add a significant load to the Central Server and might adversely affect performance of the Central Monitoring Administration
  • The BMC ProactiveNet Central Server Operations Console is optimized to handle multiple BMC ProactiveNet Child Servers collecting data. To access local data collection, you will have to switch to use the local console.

The following considerations and guidelines apply in the unlikely event of requiring such a deployment:

  • By default the BMC ProactiveNet Central Server does not show up in Central Monitoring Administration, in the list of BMC ProactiveNet Child Servers.
  • You must explicitly register the BMC ProactiveNet Central Server to itself as a BMC ProactiveNet Child Server.
  • Once the BMC ProactiveNet Central Server shows up as a BMC ProactiveNet Child Server in Central Monitoring Administration, then you can add the Integration Service to the Central Server for further configuration.

Removing or uninstalling a BMC ProactiveNet Child Server

Before you uninstall a BMC ProactiveNet Child Server, use the pw cmadmin deregisterChildServer command to remove the server from the Central Monitoring Administration list of child servers.

pw cmadmin deregisterChildServer -cmaHost=<cmaHost> [-cmaPort=<cmaPort>]
-cmaUser=<cmaUser> -cmaPasswd=<cmaPassword> [-cmaProtocol=http|https]

For details about the command, see the BMC ProactiveNet Command Line Interface Reference Guide.