Skip to main content
Skip table of contents

Update the IP Address of a Data Processor

Changing the IP Address of the Data Processor Service with minimal service interruption requires more time and planning than doing so for other LogRhythm Services. Every System Monitor assigned to the Data Processor needs to be updated for it to continue functioning properly.  Rather than manually updating every System Monitor Configuration Manger locally, LogRhythm has provided a mechanism to push the change to the System Monitors throughout the deployment.{

  1. 24 hours before you plan to change the IP address, update the SecondaryServerIP setting in the Data Processor Advanced Properties with the new IP. Changing this setting sends a secondary IP setting to all System Monitors bound to the Data Processor.
  2. After waiting 24 hours for the SecondaryServerIP setting to propagate to all System Monitors bound to the Data Processor, stop the LogRhythm Mediator Service using the Windows Services Console.
  3. If you have a stand-alone Data Processor on a distributed system, complete the following steps. Otherwise, skip to step 4.
    1. Use standard Windows procedures to change the IP address of the system.
    2. Ensure your DNS service reflects the change.
    3. Open the LogRhythm Client Console.
    4. On the main toolbar, click Deployment Manager.
    5. Click the Entities tab.
    6. To open the properties page, double-click the Data Processor host.
    7. Click the Identifiers tab.
    8. In the Identifiers field, select the old IP address and click Delete.
    9. In the IP Address field, enter the new IP address, click Add, and then click OK.
  4. In the Client Console, click the Data Processor tab of the Deployment Manager.
  5. Double-click the Data Processor.
  6. In the lower-left corner of the Properties dialog box, click Advanced.
  7. Remove the SecondaryServerIP value.
  8. Update the ServerIP value with the new Data Processor IP address.
  9. Restart the LogRhythm Mediator Service using the Windows Services Console (services.msc).
  10. In the Client Console, click Deployment Monitor on the main toolbar.
  11. Verify that System Monitors check in. They should start to show heartbeats shortly after the Mediator service is restored.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.