Historically, Broker Failover in VMware Telco Cloud Service Assurance Domain Managers ensures that if the ACTIVE broker goes down, the STANDBY broker will take its place and attach to the domain managers.

In the VMware Telco Cloud Service Assurance UI, only the ACTIVE broker is added from the Failover Environment. If this ACTIVE broker goes down, the domain managers attached to it will also disconnect. VMware Telco Cloud Service Assurance is not able to detect that the STANDBY broker has taken over in the domain manager. This disrupts the monitoring of critical notifications and topology data received from domain managers by VMware Telco Cloud Service Assurance. With the introduction of broker failover support in VMware Telco Cloud Service Assurance, this issue is resolved, ensuring uninterrupted monitoring of critical notifications and topology data from the domain managers

To configure the Failover in the Domain Managers refer, VMware Telco Cloud Service Assurance Failover System User Guide.

Scenario during broker failover

  1. The VMware Telco Cloud Service Assurance depends on the BrokerFailoverTriggered Event triggered by the Failover Manager to update the Broker and EDAA Server details in the VMware Telco Cloud Service Assurance. Hence its mandatory to underly the Failover Manager in Presentation SAM Server.
  2. In the VMware Telco Cloud Service Assurance Smarts Integration, you need to add only the Active Broker details.
  3. The ACTIVE broker is attached to VMware Telco Cloud Service Assurance, and all domain managers are connected to the ACTIVE broker.
  4. Notifications and topology data are received by VMware Telco Cloud Service Assurance from the domain managers.
  5. The ACTIVE broker goes down.
  6. The Failover Manager detects that the broker is down and promotes the STANDBY broker to ACTIVE.
  7. Once the Broker Failover is complete in the domain managers, the Failover Manager generates a “BrokerFailoverTriggered” notification in SAM.
  8. This notification is also received by VMware Telco Cloud Service Assurance from SAM.
  9. Upon receiving this notification, Event service triggers broker failover in the Platform.
  10. VMware Telco Cloud Service Assurance will now be connected to the new ACTIVE broker, and all details, such as EDAA URL and Broker IP, are updated in VMware Telco Cloud Service Assurance.
  11. The reception of notifications and topology data from the domain managers by VMware Telco Cloud Service Assurance is restored.

Failover Status:

Before Failover Screenshots:

Failover Triggered:

After Failover Screenshots