Administer the Hybrid Virtual Appliance Deployment

Perform the following steps to administer the Virtual Appliance nodes in your Hybrid Deployment:

Disable the AIOps Service

If you are using Virtual Appliance Hybrid Deployment, you require to disable the AIOps service in your Controller. Follow the steps to disable Anomaly Detection service in Administration Console:
  1. Log in to the admin.jsp page and set the below properties to false:

    • anomaly.detection.enabled

    • anomaly.detection.deployed.onprem

  2. Click Save.
After setting these properties to false, the Anomaly Detection service in the Controller is temporarily disabled. This action interrupts communication between the Controller and the Virtual Appliance.

Stop the Virtual Appliance Services

Stop appd services on the Virtual Appliance.

Complete the following steps to stop the Virtual Appliance services:
  1. Stop the Anomaly Detection, Secure Application, ATD, and OpenTelemetry services.
    CODE 
    appdcli stop aiops|secureapp|atd
  2. Run the following command to stop Virtual Appliance services:
    CODE 
    appdcli stop appd
    Note: Wait for all pods to terminate, excluding the following namespaces:
    • appd-container-registry
    • cert-manager
    • elastic-system
    • kafka-operator
    • kube-system
    • mysql-operator
    • pg-operator
  3. Run the following command to stop operators, then wait till all the pods are terminated:
    CODE 
    appdcli stop operators
  4. Run the following command on all the Virtual Appliance nodes:
    CODE 
    sudo microk8s stop

Start the Virtual Appliance Services

Start the appd services on the Virtual Appliance

Complete the following steps to start the Virtual Appliance services:
  1. Start all the virtual machines.
  2. Run the following command to start microk8s.
    CODE 
    sudo microk8s start
  3. Verify the status of virtual machines.
    CODE 
    appdctl show boot
    Note: Ensure that the status of the services in each node appears as Success.
    Sample Output:
    CODE 
    NAME             | STATUS    | ERROR
------------------+-----------+-------
 enable-time-sync | Succeeded | --
 firewall-setup   | Succeeded | --
 hostname         | Succeeded | --
 microk8s-setup   | Succeeded | --
 ssh-setup        | Succeeded | --
 storage-setup    | Succeeded | --
 cert-setup       | Succeeded | --
  4. Start the Virtual Appliance services.
    CODE 
    appdcli start appd <profile>
appdcli start aiops <profile>
appdcli start secureapp <profile>
appdcli start atd <profile>

Enable the AIOps Service

After you successfully start the services, enable the Anomaly Detection service to restore the communication between the Controller and the Virtual Appliance.
  1. Log in to the admin.jsp page and set the below properties to true:

    • anomaly.detection.enabled

    • anomaly.detection.deployed.onprem

  2. Click Save.

Generate the Hybrid Configuration File

Generate the hybrid configuration file when custom certificates are not used for Ingress and Kafka clusters.

Hybrid deployments only: Generate this file when custom certificates are not used for the Ingress and Kafka clusters

Ensure that you have the latest CA certificates obtained after installing services. If not, update the CA certificates and regenerate the hybrid configuration file after restarting the service.

  1. On the Virtual Appliance, generate the hybrid configuration:
    CODE 
    cd ~/appd-charts/utils
bash prepare-hybrid.sh

    Sample output:

    CODE 
    Writing Kafka CA Cert
Writing Schema registry CA Cert
Writing AnomalyDetectionKafkaSSLProducer
Writing AnomalyDetectionKafkaConsumerSSL
Writing configure script
Creating archive of hybrid config
hybrid-config/
hybrid-config/kafka-ca.crt
hybrid-config/AnomalyDetectionKafkaConsumerSSL
hybrid-config/configure.sh
hybrid-config/schema-registry-ca.crt
hybrid-config/AnomalyDetectionKafkaSSLProducer
Completed

    The script creates hybrid-config.tar, containing Kafka and Schema Registry CA certificates, producer and consumer SSL configuration, and configure.sh.

  2. Copy the hybrid-config.tar file to the standalone Controller.
  3. Extract and run the configuration script:
    CODE 
    tar -xvf hybrid-config.tar
  4. Change to the extracted configuration directory and run the script:
    CODE 
    cd ~/hybrid-config
bash configure.sh
  5. Enter the actual Controller home when prompted:
    CODE 
    Controller home [/opt/appdynamics/platform/product/controller]: /path/to/platform/controller
    Note:

    Virtual Appliance certificates expire after five years. Regenerate the hybrid configuration and copy updated certificates to the Classic Controller as part of certificate rotation.

    For more information on how to audit and rotate certificates in Virtual Appliance, see Manage Virtual Appliance Certificates.

  6. Restart the classic Controller.