Start Cutover Process to Redirect Agent Traffic

When the Splunk AppDynamics components reach the saturated state, you can initiate the cutover to redirect the agent traffic to Virtual Appliance. Before you begin the cutover phase, verify the migration status.

Redirect Agent Traffic to the Virtual Appliance

Set up a load balancer for your Virtual Appliance to receive agent traffic.

Ensure to complete the following tasks before starting the cutover:

Standard

  1. Configure DNS entries

  2. Disable the Default Certificate Property.

  3. Disable the Events Service SSL Property

Hybrid

  1. Disable hybrid setting in the globals.yaml.gotmpl file.

  2. Configure DNS entries

  3. Disable the Default Certificate Property.

  4. Disable the Events Service SSL Property

  1. Update the Classic On-Premises DNS to point to the Virtual Appliance load balancer. Map the classic on-premises port to VA port as follows
    Classic On-Premises Virtual Appliance
    8181 443
    9080 32105
    7001 80
  2. Restart the Synthetic server.
Once these steps are completed, the data migration is finalized, and you can begin using the Virtual Appliance to monitor your applications with the data previously present in Classic On-Premises.