Master-to-slave replication

Master-to-slave replication provides automatic replication of the selected customized data types from one or more designated master HMCs to one or more designated slave HMCs.

To set up a master console, do the following:

  1. Log in the HMC using a user ID that has administrator roles.
  2. From the HMC Management work pane, click Manage Data Replication.
  3. Select Enable, then click Save.
    Note: If you want to configure additional master consoles, see Peer-to-peer replication
To set up the slave console, do the following:
  1. Log in the HMC using a user ID that has administrator roles.
  2. Select Manage Data Replication.
  3. Select Enable.
  4. Click New.
  5. Complete one of the following steps:
    • Select an HMC to be used as a master data source from the list, then click Add.
    • In the TCP/IP Address Information field, enter the TCP/IP address of the HMC to be used as the master data source, then click Find.
  6. Select the types of data that you want to accept from the HMC.
    Note: When configuring a HMC as a slave, you should check the types of customizable data from the Local Customizable Data Change Warnings list that should generate warnings to a user when manual changes are made to that data on this HMC. Manually updating data on the slave HMC will change the local data level to a higher level than the master. Changes on the master HMC will then not replicate to this HMC until the master data level exceeds that on the slave, or a Sync from Master or Push to Slaves task is run to resynchronize the data levels on master and slave.
  7. Choose one of the following actions:
    • Click Save to close the Manage Data Replication window.
    • Click Push to Slaves to transfer all local levels to any communicating slave. The slaves, if they are running this level of code, are instructed to accept the levels from the master, regardless of the value of their current levels.
    • Click Sync from Master to invalidate the local levels for all properties that are defined to have a master. This results in an immediate level set where the masters provide their levels to the local machine. This option is not available if the local Hardware Management Console is not defined to have any data sources.
    • Click Status to show the status of this task on this machine.
  8. Repeat these steps on any additional HMCs that you want to configure as a slave.
  9. Once communication is established between all of the HMCs, the master consoles remains synchronized with each other, providing redundancy in the event that one of the master consoles becomes unavailable. The slave consoles are kept synchronized with whichever master console provides the data to them first.

Last updated: Fri, December 06, 2019