Enable or Disable Two-Site Redundancy Support

10 Enable or Disable Two-Site Redundancy Support

This chapter provides information about how to enable or disable Two Site Redundancy feature.

10.1 Enable Two-Site Redundancy Support

To enable the Two-Site Redundancy, follow the steps outlined below:

Prerequisites

Two independent centralized sites with network connectivity are required for enabling the two-site redundancy feature. Note: only IPv4 network is supported.
Both sites must have different databases.
Both clusters should be able to communicate with one another.
All changes in charts should be done in the management group Helm charts.
Certificates for Redundancy Service must be created.
TLS and mTLS should be enabled for both primary and secondary sites. For information, see Implementing OCNADD Security Recommendations and Guidelines, TLS Configuration, and MTLS Configuration sections in Oracle Communications Network Analytics Suite Security Guide.

Update Parameters in Helm Chart

Note:

If the OCCNE cluster is LBVM based, then set cnlb.redundancyagent.enabled to false in the ocnadd-management-custom-values.yaml.

If Egress Annotation is Required: (skip this if CNLB-based OCCNE cluster is used)

If CNE version requires Egress Annotation to allow traffic outside the cluster, the below parameter should be set to true on both the mated sites:

Step 1: Go to the release folder and edit the ocnadd-common-custom-values.yaml created for management group installation.

Step 2: Set global.ocnaddredundancyagent.egress to true.

Step 3: Run helm chart upgrade:

helm upgrade <release_name> <management_chart_path> -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml -n <management_namespace>

To enable Static LoadBalancer IP of Redundancy agent:

If the user wants to enable static LoadBalancerIP for the redundancy agent, then set the below parameter to true and provide the static IP:

ocnaddmanagement.ocnaddredundancyagent.ocnaddredundancyagent.staticLoadBalancer.enabled: false           ## Change this to true
ocnaddmanagement.ocnaddredundancyagent.ocnaddredundancyagent.staticLoadBalancer.staticIP: 10.10.10.10    ## Update this with static IP

Step 1: To enable Two Site Redundancy feature in the primary site, perform the following steps:

Go to the release folder and edit the ocnadd-common-custom-values.yaml created for management group installation:

global.ocnaddredundancyagent.enabled: false         ## Change this to true

global.deployment.primary_site: false               ## Change this to true

Note:

When Oracle Communication Certificate Manager (OCCM) is used to create the TLS certificates, the following steps need to be performed to enable/disable two site redundancy instead of running helm upgrades at Step 2 & 6.

See the section Adding/Updating Loadbalancer IPs in SAN through OCCM in Oracle Communications Network Analytics Data Director Installation, Upgrade, and Fault Recovery Guide to update the Redundancy Agent's Load balancer IP in the certificate.

Since OCCM is used to create the certificates, skip steps 4 and 8.

Step 2: Run helm upgrade in Primary Site:

helm upgrade <management-release-name> -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace <release-namespace> <helm_chart>

For example:

helm upgrade ocnadd-mgmt -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace ocnadd-deploy ocnadd

Step 3: Verify the deployment post helm upgrade:

kubectl get po,svc -n <management-namespace>

For example:

kubectl get po,svc -n ocnadd-mgmt

NAME                                          READY   STATUS             RESTARTS        AGE
pod/ocnaddredundancyagent-ffddd67b9-nrkrh     1/1     Running            0               64m

NAME                             TYPE           CLUSTER-IP        EXTERNAL-IP    PORT(S)                           AGE
service/ocnaddredundancyagent    LoadBalancer   10.233.63.98      10.25.219.64   13000:32421/TCP,9000:32676/TCP    35d

After the upgrade, the ocnaddredundancyagent service should have an External-IP assigned to it, and the pod should be in a running state.

Step 4: Follow the procedure Updating SAN Entries Using Script in Oracle Communications Network Analytics Data Director Security Guide to update the External-IP obtained in the previous step.

Step 5: Now, enable Two Site Redundancy feature in the secondary site, perform the following steps:

Go to the release folder and edit the ocnadd-common-custom-values.yaml created for management group installation:

global.ocnaddredundancyagent.enabled: false         ## Change this to true

global.deployment.primary_agent_ip: 10.10.10.10     ## Change this to External-IP of ocnaddredundancyagent service set in Primary, for example: 10.25.219.64

Step 6: Run helm upgrade in Secondary Site:

helm upgrade <management-release-name> -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace <release-namespace> <helm_chart>

For example:

helm upgrade ocnadd-mgmt -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace ocnadd-deploy ocnadd

Step 7: Verify the deployments in Secondary Site:

kubectl get po,svc -n <management-namespace>

For example:

kubectl get po,svc -n ocnadd-mgmt

NAME                                          READY   STATUS             RESTARTS        AGE
pod/ocnaddredundancyagent-ffddd67b9-nrkrh     1/1     Running            0               64m

NAME                             TYPE           CLUSTER-IP         EXTERNAL-IP     PORT(S)                           AGE
service/ocnaddredundancyagent    LoadBalancer   10.233.24.112      10.25.225.149   13000:32421/TCP,9000:32676/TCP    35d

After the upgrade, the ocnaddredundancyagent service should have an External-IP assigned to it, and the pod should be in a running state.

Step 8: Follow the procedure Updating SAN Entries Using Script in Oracle Communications Network Analytics Data Director Security Guide to update the External-IP obtained in the previous step.

Step 9: Proceed to OCNADD UI to create Mate Configuration for the available worker groups. See Redundancy for more details.

10.2 Disable Two-Site Redundancy Support

To disable the Two Site Redundancy, perform the following steps:

Step 1: Delete the mate configuration for each of the mated worker group pairs from the Primary site UI.

Step 2: (Optional) Perform the cleanup on the secondary site by removing the consumer feed, filter, Kafka feed, and correlation configuration. This step can be skipped if the user wants to keep the configurations.

Step 3: To disable Two Site Redundancy feature in the secondary site, perform the following steps:

Go to the release folder and edit the ocnadd-common-custom-values.yaml created for management group installation:

global.ocnaddredundancyagent.enabled: true         ## Change this to false

Step 4: Run helm upgrade in Secondary Site:

helm upgrade <management-release-name> -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace <release-namespace> <helm_chart>

For example:

helm upgrade ocnadd-mgmt -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace ocnadd-deploy ocnadd

Step 5: Verify that ocnaddredundancyagent service and pods are removed from the management namespace of the secondary site:

kubectl get po,svc -n <management-namespace>

Step 6: Now, to disable Two Site Redundancy feature in the primary site, perform the following steps:

Go to the release folder and edit the ocnadd-common-custom-values.yaml created for management group installation:

global.ocnaddredundancyagent.enabled: true         ## Change this to false

Step 7: Run helm upgrade in Primary Site:

helm upgrade <management-release-name> -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace <release-namespace> <helm_chart>

For example:

helm upgrade ocnadd-mgmt -f ocnadd-common-custom-values.yaml -f ocnadd-management-custom-values-mgmt-group.yaml --namespace ocnadd-deploy ocnadd

Step 8: Verify that ocnaddredundancyagent service and pods are removed from the management namespace in the primary site:

kubectl get po,svc -n <management-namespace>