IBM Support

QRadar: Migrating an App Host from one deployment to another

Troubleshooting


Problem

This article describes migrating data from an older QRadar App Host to a new App Host that uses the existing IP address or hostname. The Console and managed host appliances are not impacted. The instruction in the article is not intended for High Availability appliances.

Resolving The Problem

Before you begin
  • Record the network information from the old App Host appliance as the administrator needs to manually type the information into the new appliance's network configuration.
  • It is recommended the administrator have a recent backup of the application data on the App Host. Refer to the link for more details on: Backing up and restoring app data
  • The software version of the new App Host must match the software version of the Console. QRadar does not allow appliances at different software versions.
  • Apps that are stopped will not consume memory or CPU resources. Make sure all your apps are stopped before performing these procedures.
  • Ensure there is enough disk space on the console's /store partition for the app Host app data.
    On the App Host run the command:
    # du -h /store/docker/volumes/
    On the console ensure /store has enough space based on the previous output from the App Host
    # df -h 
    For information on App Host disk space, refer to App Host disk space recommendations

Step 1: Preparing your old App Host

  • Stop the apps currently running on the App Host

    Note: after the apps are stopped, their tabs will no longer be visible in the UI.

    1. Use SSH to log in to your QRadar Console as the root user.
    2.  SSH from the Console to the App Host.
    3. On the App host, run the following command, which will print out a list of apps installed on their 4-digit app ID:
       /opt/qradar/support/recon ps
    4. After you made notes of all the App IDs, log in to the Console as an admin user.
    5. Click the navigation menu (☰) > Interactive API for Developers.
    6. Expand gui_app_framework.
    7. Expand applications.
    8. Click application_id.
    9. Click POST.
    10. In the Parameter application_id, enter an App-ID gathered from before and enter "STOPPED" in the status parameter.
    11. Click on "Try It Out" and ensure you get a 200 status response.
    12. Repeat previous steps until all apps are in a "STOPPED" state.

    image 8613

  • Migrate the apps back to the console
    1. Log in to the Console as an admin user and navigate to Admin > System and License Management.
    2. Expand "Apps are set to run on the App Host".
    3. Click on "Click to change where apps are run" and then choose "Migrate to Console."
    4. During the process, all apps and their data get copied back over to the Console.
      image 8614
  • Remove old App Host from deployment
    1. Log in to the Console as an admin user and navigate to Admin > System and License Management.
    2. Click the entry for the App Host, so it's highlighted.
    3. From Deployment Actions Choose Remove Host.
    4. When prompted, click Remove to confirm the removal of the host from the deployment.
    Results
    After these steps are completed, your old App Host is removed from the deployment. The app data resides on the Console. The apps are in a "STOPPED" state.

Step 2: Reassigning IP addresses on appliances

After the App Host is removed from the deployment, administrators can change the IP address of the old App Host to an unused or decommissioned IP range. Changing the IP address or hostname of the old App Host ensures that if the decommissioned host is ever powered back on, it does not cause packet collisions in the network.

Note: IP address changes are not allowed over SSH connections. An IP address change can be completed by connecting with remote KVM, IMM, XCC, or a VM's Console to prevent connection and lockout issues.

  • Reassign the IP address of the old App host to a decommissioned IP address range

    This procedure reassigns the IP address of the old App Host to a decommissioned IP address space to free up the existing IP address for the new App Host.
    Important: Please refer to the Flash Notice on qchange_netsetup before performing this procedure.

    1. Connect to the App Host with a remote KVM for access to the local Console keyboard and log in to the old appliance's command line as the root user.
    2. To reassign the old App host's IP address, type /opt/qradar/bin/qchange_netsetup to change the IP address to a decommissioned IP range.

  • Setting the IP address for the new hardware

    This procedure assigns the existing IP address to the new App Host to be added to the deployment with the old  IP address.

    1. Connect with remote KVM for access to the local Console keyboard, log in to the command line interface of the new App Host as the root user.
    2. From the new App Host's command line, type /opt/qradar/bin/qchange_netsetup to use the same hostname and IP address as the old App Host.
    Results
    The IP addresses and hostnames are updated for both App Hosts. The administrator can now add the App Host to the QRadar deployment.

Step 3: Adding the new appliance to the deployment

Note: The new App Host must be at the same software version of QRadar Console.

  1. Log in to the QRadar Console as an administrator.
  2. Click the Admin tab and select the System and License Management icon.
  3. Click Deployment Actions > Add Host.
  4. If prompted to add old components from the deployment to the host, select Yes.
  5. Click Save and Close.
  6. From the Admin tab, click the Deploy Changes icon.

Results
After the host is added back to the QRadar deployment, the deploy process ensures that the required configuration is regenerated on the new appliance.
 

Step 4: Migrating apps to new App Host

  1. Log in to the Console as an admin user and navigate to Admin > System and License Management.
  2. Expand  "Apps are set to run on the Console".
  3. Click on "Click to change where apps are run" and then choose "Migrate to App Host."
  4. During this process, all apps and their data will get copied back over to the App Host.
  5. Once the migration is complete, click the navigation menu (☰) > Interactive API for Developers.
  6. Expand gui_app_framework.
  7. Expand applications.
  8. Click application_id.
  9. Click POST.
  10. In the Parameter application_id, enter an App-ID gathered from before and enter "RUNNING" in the status parameter.
  11. Click on "Try It Out" and ensure you get a 200 status response.
  12. Repeat previous steps until all apps are in a "RUNNING" state.
  13. Verify that the app tabs now show up and are accessible.

Results
The apps are running on the new App Host. The migration is complete.
 
Important
If any of the apps display a message similar to: "Cannot establish secure connection to the console. Check if your QRadar Certificates are setup properly" or a similar message after the migration, refer to the article: QRadar application error: 'Cannot establish secure connection to the console. Check if your QRadar Certificates are setup properly'

Document Location

Worldwide

[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwt3AAA","label":"QRadar Apps"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.3.3;7.4.1;7.4.2"}]

Document Information

Modified date:
15 March 2021

UID

ibm16414807