Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In some cases maybe you Sometimes, you may want to change a slave remote site to become the mastercentral site.

Step-by-step guide

  1. On the mastercentral site: Go to Distributed Monitoring -> Edit the slave connection and deselect 'Disable configuration via WATO on this site' (if selected)
    1. Now your slave remote site has an its own WATO

  2. Now you need to move all hosts from master central to slaveremote
    1. On the mastercentral site: Go to WATO -> Hosts and edit all hosts. You need to select at 'Monitored on Site' for your slaveremote site. Please save and activate the changes.
    2. You need to do a rediscovery for all hosts
    3. Now your slave remote site is monitoring all your hosts

  3. On the mastercentral site: Go to Distributed Monitoring and remove the slave remote Connection.

  4. On the slaveremote site: Go to Distributed Monitoring and add create a connection for the mastercentral site.
    1. Please Note: If you enable 'configuration push,' the slave remote site will override the mastercentral site. Please make sure that ensure you have all rules/settings already on your slaveremote site.

  5. After activating all changes, the master central site is not monitoring any host. Please repeat step 2 if you want to monitor the host via mastercentral.

  6. Now you've successfully promoting slave to masterpromoted remote to central.


Filter by label (Content by label)
showLabelsfalse
max5
spacesKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("distributed_monitoring","slave_to_master") and type = "page" and space = "KB"
labelsdistributed_monitoring slave_to_master

...