Page tree
Skip to end of metadata
Go to start of metadata

After you install an Infrastructure Management server as a Central Server, use the following procedure to configure a Central Server to collect data from Child Servers.

To configure a Central Server to collect data

  1. On a server designated as the Central Server, open the mcell.dir file, located in the installationDirectory\pw\server\etc directory.
  2. At the end of the file, add a line for each Child Server with the following cell server information, then save and close the file:

    cell childCellName mc cellHostName:cellPort
      • childCellName is the name of the Child Server Cell.
      • cellHostName is the name of the Child Server host.
      • cellPort is the cell port

        For example:

        cell pncell_01 mc 01_server.bmc.com:1828
  3. To reload the mcell.dir file with the updated information, open a command prompt and enter:
    • mcontrol -n centralCellName reload dir

      centralCellName is the name of the Central Server Cell.
  4. On the Central Server, open the serverlist.xml file, located in the installationDirectory\pw\pronto\conf directory.
  5. For each Child Server, type values under the <OriginatingProactiveNetServer> element. 

    The information for <cellname> and <hostname_or_ipaddress>are the same as those entered in step 2.

    <OriginatingProactiveNetServer>
    	<cellname>pncell_01_server</cellname>
    	<hostname_or_ipaddress>01_server_bmc.com
    	  </hostname_or_ipaddress>
    	<serverport></serverport>
    	<protocol></protocol>
    </OriginatingProactiveNetServer>
    • pncell_01_server is the name of the Child Server Cell.
    • 01_server.bmc.com is the name of the Child Server host.
    • If you use the default server port, 80 (for HTTP), you can leave this element blank; otherwise, type the server port.
    • If you use the default protocol, HTTP, you can leave this element blank; otherwise, type the server port.
  6. Save the serverlist.xml file.
  7. For device aliases that were manually added to Child Servers, manually add the device aliases to the Central Server, too, to ensure that events are associated with the appropriate devices.
  8. In the Event View of the Central Server, click the Refresh icon (not the browser Refresh), or wait for the screen to refresh automatically.

    Events from the Child Servers are displayed in the Central Server.

    Note

    When an originating BMC TrueSight Infrastructure Management Server receives events in a blackout period, the events are not propagated to the Central Server.

Related topics

Infrastructure Management multiple-server deployment architecture